jkulawik
jkulawik
Well, after trying to make a pull request for this, it seems that the issue is that the autoload is called in classes which don't inherit from node, e.g. Resource...
I've worked on this a bit more and here's what I found. The remaining (i.e. in code which doesn't inherit from Node) direct `CyclopsAutoload` usage consists of 6 calls to...
I mean the entire project from this repo. When I launched it the first few times, I got many errors (mostly related to GUT if I remember correctly) and cyclops...
One thing that could be an issue with this is that when selecting a scene which has CyclopsBlocks (and not that object alone), it might go into the Cyclops editor...
Unrelated to this issue, but if CyclopsBlocks is being deprecated, will `1.0.2` have backwards compability?
The mention on instance_id being only usable in the current session was added to the docs somewhere along the way - it's there now. While this might be useful to...
One major caveat I just realized is dynamically spawned nodes - they won't be in the level scene and as such cannot be reinstantiated, even if they have proper names...