I've thought about this confusing behavior a lot, and to me it seems like the only sane way to fix it is by making trigger objectives disabled by default. First, let's look at the situation:
- Set up a trigger objective:
- Try to trigger it:
→ "You cannot trigger this objective yet"
- Enable the objective:
→ "Nothing changed, that trigger is already enabled"
- Try another time to trigger the objective:
→ This time, it works!
Now, why does it work in step 4, but not in step 2? Because step 3 initialized the objective, which seems to be WAI considering a bug related to exactly this behavior was fixed recently (
Note that this situation changed slightly from 1.12.2, in that enabling a trigger objective always succeeded in 1.12.2, even if it was already enabled.