@onready that's called after base class @onready

[feois]

Could be a boolean toggle like @onready(after := false)

[Mickeon]

What do you need this for? Most of the times, it's not necessary to assign before _ready() is called, and when it is, it's usually better to be explicit about it and assign the variable within _ready() itself.

[feois]

# Base class

@onready var x := MyClassX.new()
@onready var y := MyClassY.new(x)
@onready var z := MyClassZ.new(x, y)

# Subclass

# not working
@onready var y2 := MyClassY.new(x)
@onready var z2 := MyClassZ.new(x, y)

of course i can just do it in _ready() but @onready is just way cleaner

[theraot]

This is making me think that the derived class onready should always go after the base class onready. Because the derived class onready can depend on the base onready. But at no point the base class onready can depend on the derived class onready.

Is there any case where having the onready of the derived class run after would cause problems?

[AThousandShips]

This is implemented here, looking through the history but I suspect it's for simplicity, to not have to implement some stack to call it in that order

Implemented in:

• GDScript: Use implicit method for @onready variables godot#62255

To solve a different issue where onready variables weren't ready by _ready

[dalexeev]

The current behavior was considered a bug and fixed for future 4.3:

• @onready vars from inherited scripts are initialized after ones from the inheriting scripts godot#63329
• GDScript: Call implicit ready on base script first godot#91364