I have a feature request:
It would be very useful if I could disable single actions (single “lines”?) as you can for an entire event.
I miss it every time I have to debug a complex event where I need to try different actions to get things working.
lol… oops, …mmh …sorry…
anyway,
it’s more a matter of “organization” in your case.
I think that even with the feature you’re asking for,
it would still be pretty tough to find an error in there…
not that there aren’t any.
@RMDB I believe you misunderstand me
In my screen shot I may want to play around with the calculations on this line:
![]()
or substitute it with something different, but I want to keep that rather complex calculation for backup. I would like to copy that line, disable the original and then play around with the copy and perhaps disable the delete XPBubbles line like so:
I think this feature would also require some clear indication on the left side of the events editor to signal that an individual action was disabled in the event to avoid people forgetting.
What I normally do in case I need to disable something in the middle of a large event, I create a copy of the entire event, disable the original event and delete the action from the copy. Once I’m done with it, I delete the copy which I no longer need.
thaz fine…
anyway
I’m more worried about the wait actions being repeated every frame…(at least from your ss) and some creat/delete in real time…i doubt the local would make things works as trigger once there…but i may be wrong about it.
Yeah, same here.
I think it’s a pretty common approach to test and avoid messing up the events.
Anyway, the request is interesting in my opinion…
as long as it’s used properly
Dito for me too.
A+
Xierra



