Page MenuHomeFeedback Tracker

Little backward incompatibility for triggers
New, NormalPublic

Description

Hi,
It took me some times to understand why some of my triggers didn't work anymore. I used one as countdown only, for altering the color of the main display. (See more info at http://steamcommunity.com/sharedfiles/filedetails/?id=864939640&tscn=1490378620 , thanks to KLG Finski feedback).

In fact, since 1.68, something must be written (returning true or false) in trigger condition. I used to let totally blank (erase this) on trigger condition if I didn't need a condition (delayed script with countdown for example). till 1.66 this field could be empty and the trigger always fired. Now, you must write at least: true to make the trigger work. I admit my bad for a weird usage of the condition field but something has truly changed for triggers and their behaviors. I didn't test all of them.

I hope this could help some other "lazy" scripters as me.

Details

Severity
Minor
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
General
Steps To Reproduce

edit a player
add a trigger with nothing (blank) condition field
hint "OK" in on activation field

in 1.66 this trigger is always fired
in 1.68, this trigger doesn't work anymore

Add true in condition field, this trigger is now operative and always fire.

Event Timeline

PiepMGI created this task.Mar 24 2017, 11:19 PM