Piston keeps running over and over again when Testing

[nh.schottfam]

What is happening is your piston has no triggers.

By default, in a piston with no triggers, webcore promotes conditions to triggers.

Your condition is @TestInt, ie every time the global value changes you are getting an event.

pausing the piston in the IDE will stop it...

See:

Some webCoRE Basics for writing pistons - Triggers / Conditions

I regularly see questions of folks having trouble getting a piston to work properly. Many times it is incorrect ordering / use of trigger comparisons (displayed with lighting bolt in webCoRE UI) This example follows 'best practices': [image-3] Few things to note from this piston: In the first if statement (line 21), there is one trigger comparison (since it uses AND; more than one trigger events can never occur at same time), and a condition comparison. (You can have multiple trigger co…

Some webCoRE Basics for writing pistons - Trigger aggregation

This is another example of using triggers in a webCoRE piston As many of you may know, if a piston does not use any trigger comparisons, webCoRE will attempt to upgrade condition comparisons to a trigger (subscription). If your piston only uses condition comparisons, many times this is an easy way to code (ie only use condition comparisons). The challenge sometimes, is you need/want a trigger comparison, and now all your condition comparisons are no longer subscribed to (automatically as …

I'll check if treating the switch as a condition is correct, so far it looks correct as that could have been a device:attribute value

you can adjust the piston setting for subscriptions to set to never so it does not subscribe to anything.

I think you could also create a local integer variable i

set variable {i} = @TestInt

switch (i)