Asterix Gaming Guild Logo GeneralXXLXXL 2XXL 3XXXLOlympic GamesXXL EditorToolsOff-TopicXXL RomasteredXXL 2 RemasteredOther GamesModsCaesar's ChallengeUnfair XXLPatchesFan ArtPersonal ArtSpeedrunningMediaRandomizerBETA RomeHSKALPresence AdrienPresence SPQRSupport Bot Helpdesk

#editor

adrientd
For events it doesn't look for superclasses (iirc), you have to use the "event sets" instead to duplicate events across classes
adrientd
And yeah I also noticed that you defined some events to the CKHkHero, but they do not show up
pegperegogaucho
Yup, I don't think using the includesets is the correct way to go about this though...
pegperegogaucho
Because it makes sense for doors since they for some reason have no common superclass except the hook itself
adrientd
Yeah indeed it might make sense to just take from the superclass.
adrientd
It's just that right now there is no way to obtain the superclass of a class :Obelul:
adrientd
Apart of calling isSubclassOf with every class possible.
adrientd
But either I could write it in the Json, or maybe keep a typedef of the parent when using CKSubclass
adrientd
Not something I would do right now though :Obelul:
pegperegogaucho
You could make a type alias using Superclass = T;
pegperegogaucho
Tomorrow I will try to get some properties documented, because I've already had some moments while making Beta Rome where I forgot what some property does and had to look through text documents again :Obelul:
pegperegogaucho
A useful feature would also be an option to hide undocumented properties and only show them when some option is enabled to make the interface easier to use
pegperegogaucho
There really is no reason to, for example, change the references of many hooks like enemies, it should all just be automatic
pegperegogaucho
And also I can't believe that there is no option to delete choreokey spots yet? 🙈 I though I was going crazy when I couldn't find the delete button
adrientd
lmao indeed, but you can press the Delete key to delete a spot for some reason
adrientd
Absolutely, some properties don't make sense to be shown
adrientd
That would make sense if there's already a big amount of properties being documented, because otherwise if it always hide by default and a useful property is documented, then no chance to change/see it. But we could definitely try that.
adrientd
In the reflection system there's already some flags for the properties, one of which is a hide flag. These flags should be exposed and be able to be changed in the json (and not just in the code).
adrientd
Ok I'm about to push to the repo if that's ok?
adrientd
Doing this from github.dev (VSCode basically) because I'm too lazy to open Visual Studio :Obelul: