Hi, so it depends on what is causing this "doOnTrigger".

It will continue to create these messages as long as the "doOnTrigger" is triggered.

Can you post me the json which contains the doOnTrigger?

{
"conditions":[
{"exist":{"tag":"chimaera","quantity":1,"differentSpec":true,"insert":true}}
],
"doOnTrigger":[{"sideObjectiveAvailable":"opt_smallspine"},
{
"message": {
"id": "merchant_pudgy_cuskeel",
"inserts": [
"pudgy_cuskeel",
"*pudgy_cuskeel"
],
"buttons": [
{
"req": {
"conditions": [
{
"haveMoney": {
"quantity": 7500
}
}
]
},
"doOnClick": [
{
"money": -7500
}
]
}
],
"enclosedCreateOne": [
"pudgy_cuskeel",
"pudgy_cuskeel"
],
}
},
{
"message": {
"id": "merchant_batangas_groppo",
"inserts": [
"batangas_groppo",
"*batangas_groppo"
],
"buttons": [
{
"req": {
"conditions": [
{
"haveMoney": {
"quantity": 4800
}
}
]
},
"doOnClick": [
{
"money": -4800
}
]
}
],
"enclosedCreateOne": [
"batangas_groppo",
"batangas_groppo",
"batangas_groppo",
"batangas_groppo",
"batangas_groppo",
"batangas_groppo",
"batangas_groppo",
"batangas_groppo"
],
}
},
{"unlock":"glauerts_frogfish"},
{"unlock":"western_pacific_toungefish"}
]
},

This is basically what the original code look like

So I'm assuming that is under either "globalTriggers" or an individual section's "triggers". Either way the trigger should only go off once unless reset by an "activateTrigger" command from somewhere else.

I'm sure there is a reason why the trigger is going off multiple times, I think you'd better send over your whole file if you don't mind? I'll find the important bit and create a test harness at my end and see if I can figure it out.

You can send it to support@twicecircled.com. :)

Originally posted by Twice Circled:

So I'm assuming that is under either "globalTriggers" or an individual section's "triggers". Either way the trigger should only go off once unless reset by an "activateTrigger" command from somewhere else.

I'm sure there is a reason why the trigger is going off multiple times, I think you'd better send over your whole file if you don't mind? I'll find the important bit and create a test harness at my end and see if I can figure it out.

You can send it to support@twicecircled.com. :)

No problem

It is an individual "trigger" (under the initial main section).

Also, pretty sure there is a nested trigger in the "globalTriggers" that may or may not meet the criteria of the above. At least the nested is there around line 788 in the latest from the Workshop (which doesn't have this issue). Unsure how/if that affects the issue (but is not good, IMO).

Right I think I understand now. When a doOnTrigger hits an error while carrying out the actions, it never marks itself as being triggered, so it will continue to be triggered over and over.

Check the error log:

Windows: C:\Users\<insert username>\AppData\LocalLow\Twice Circled\Megaquarium\player.log
Mac: ~/Library/Logs/Twice Circled/Megaquarium/Player.log
Linux: ~/.config/unity3d/Twice Circled/Megaquarium/Player.log

And you will get a good clue as to the problem.

It's probably one of the unlock actions at the end, one of the specs probably doesn't exist due to a typo?

{"unlock":"glauerts_frogfish"},
{"unlock":"western_pacific_toungefish"}

Thx you!

Thanks for explanation and good prediction. Was typo in the bugged version:
galuerts vs glauerts.