Yagira
commented
1 year ago This is actually a bunch of issues combined.
- Events don't actually have any values until you set them yourself, the values that you see by default are just placeholders displayed in the editor. They are also often different from what the events fallback to when the value doesn't exist (editor shows 0 but the event uses 0.1).
- The argument values are a list so if a value is missing they will get assigned to the wrong arguments, the in-editor order is also different from the actual argument order. On your video the 'hide in editor' is first but it is actually the last argument.
There's a bit more but this is roughly what happens. I guess the easiest solution - without reworking the whole argument thing - is to just set default values on every event so they always exist. I guess I can add that for the command event and we will see how that works.
pingu7867
it affects command's "hide in editor", ranger's "npcs and players only", etc. and affects both the workflow ingame and what eventually gets (not) saved if you miss it.
On closer inspection, the arguments aren't being registered in the editor unless of certain conditions. I've done some tests by doing actions at different orders.
https://user-images.githubusercontent.com/3782245/210969540-989a06a5-f590-463f-b1fc-43d910c7fd8b.mp4 video if that's any help.
with ranger, touching distance then checking the tickbox doesn't register the boolean and compare isn't registered either; touching compare registers both and allows the tickbox to be registered;
seems the boolean only gets registered if all number values, or the final/bottom number value in the list get registered / touched