Closed rijuma closed 1 week ago
Thanks for these! I'll merge this with some other fixes later this summer. No time ATM.
We decided against these additions. Although handy and powerful they are quite complex and a bit too cumbersome for the average user.
That's understandable. I was just checking this today to close it since as you've said, the edge use case doesn't quite worth the complexity.
I hope I can come up with some real helpful ideas in the future.
New stuff added
Entity:
trigger_counter
Params added
message_complete
: Message to show when the sequence is complete. (default: "Sequence completed!")message_more
: Message to show when there are more to go. This has precedence over the partials. (default: "There are more to go...")message_more_a
: First part of the more message variant.message_more_b
: Last part of the more message variant.message_count
: Message to show when there are few to go. This has precedence over the partials.message_count_a
: First part of the count message variant. (default: "Only")message_count_b
: Last part of the count message variant. (default: "more to go...")message_one
(optional): Custom message when only one remains.count_more
: If more than this quantity remains, the more message is used. Otherwise uses the count message. -1 to always use count variant. (default: 3)Params removed (from fgd y def) files
wait
: If you check progs_dump's current code, it basically sets the wait to -1 disabling its behavior. No use being shown in the editor.message
: Since it now has several message parameters, I use it as an alias formessage_complete
for backward compatibility, but I removed it from the editor to discourage its use since it's clearer this way.Extra notes
I know splitting the values for the pre and post message it's cumbersome, but there are no string handling functions available without adding dependencies, so this is the best I could do.
Test map
trigger_count_test-v0.2.zip
Screenshots