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

#editor

adrientd
Ah ok, in that case 8 could be "Respawn n enemies" and 20 "Respawn until n". Not sure how I could phrase them better :LUL:
pegperegogaucho
Sounds good!
pegperegogaucho
Also rename 19 then, since it's exactly like 8 but the enemies will always spawn directly behind asterix even if spawn markers are defined (normally 8 and 20 would spawn enemies at a fitting marker)
adrientd
Ok
adrientd
And I think that makes more sense
adrientd
I guess that the U1 and U2 numbers in the pool could be just named "Initial spawn count"
adrientd
And I wonder do you know if there is a difference between U1 and U2?
adrientd
Because if they are always the same, might as well just show one of them and update them both at the same time.
pegperegogaucho
That is a very good question which I unfortunately do not have an answer for :LUL:
adrientd
Yeah, that would need some checking
adrientd
Also I think we could guess (unless some unknown action contradicts it) that the "int1" parameter type is an index to some list (be it the choreographies, pools, comparators, ...) and could be represented with a combo box, whereas "int0" is just some integer that can be freely chosen.
adrientd
But the state index for switching between them is "int0" though.
adrientd
I think I might add some new JSON key to the parameter that indicates which list the "int1" parameter refers to.
adrientd
So for example user would get a combobox of possible comparators instead of having to enter a number.
adrientd
But I wonder if I should look into the events first :FrogThinking:
pegperegogaucho
Was thinking about that as well, I think the game doesn't really care if the type is int0 or int1, so maybe we could just make the state index int1 and proceed to use a dropdown :LUL:
pegperegogaucho
For actions 6 and 7 only < and > is defined as the others don't make much sense for float values
adrientd
Yeah, I could always make dropdowns for "int0", anyway it won't matter much
adrientd
Not sure if it would be useful to enumerate the possible values (for comparators) in the JSON or just put them in the code, noting that lists such as choreo indices still need to be handled by the editor itself anyway.
adrientd
And unsure if comparators would be the only things that would use it, and if it's worth doing it :LUL: