Piston Inconsistency with Event Controller (1.204.017 b0)
Steps to reproduce:
1. Build piston, event controller, interior light on shared grid
2. Set event controller to toggle light on/off based upon piston position % threshold 96%
3. Set piston max distance to 10m
4. Manually toggle reverse on piston to demonstrate light turning on/off after passing threshold
5. Set piston max distance to 5m
6. Manually toggle reverse to demonstrate light does not turn on/off after passing same distance, instead passing 96% threshold of newly set 5m distance.
7. Calculation should denote that upon changing piston max distance to 5m piston position % has increased beyond 100% value
Windows Version: Windows 10 22H2, Build 19045.4412
Description:
The use of the variable (user facing) "Piston Position %" in Control Panel -> Event Controller -> Event (drop down) provides a threshold percentage ranging from 0% to 100%. This implies that the "Piston Position %" relies upon a percentage calculation ranging from 0 meters (0%) to 10 meters (100%). However, changing the variable (user facing) "Maximum Distance" in Control Panel ->Piston -> Maximum Distance (slider) alters the total percentage calculation to 0 meters (0%) to "Maximum Distance" (100%).
The issue exists in not being able to define the limits and actions of the event controller to perform as expected given potential changes in the environment. If a user attempts to increment the extension of a piston by making use of the predefined variables accessible to the Event Controller extension or retraction mechanics will perform differently depending on environment variables.
Proposed solutions:
1.) Define the "Piston Position %" as the physical limits of the piston. If required, add additional variable to track the "Max Distance %" (potentially also the "Min Distance %").
2.) Add "Increment/Decrement" mechanics similar to the "Increase/Decrease Max Distance" mechanic such that one operation of the new mechanic extends or retracts the piston by a set value. Reference here is the pre-existing 0.5m increment used in the hotbar menu for pistons Increase (decrease) Maximum Distance.
Either or both proposed solutions may resolve the issue. If the issue describes game mechanics functioning as intended please disregard.
I have the same bug
Hello, Daniel!
Thank you for writing to us.
We tried to replicate the issue following the steps you shared, and the light did turn ON/OFF even when changing the Piston Max Distance to 5m.
Since the issue didn't occur on our end, could you kindly share further information with us? Did you experience this issue on a modded world/server (with active MODs/Scripts) or a vanilla world/server (without any active MODs/Scripts)?
If the issue occurred in a modded world/server, please create a blueprint of your affected grid, paste it in a vanilla world/server, and check if the issue still persists. If it doesn't, the issue you experienced might be caused by the MODs/Scripts.
However, if the issue still persists in a vanilla world/server, please send us a screen recording/video showing the issue and the blueprint of the affected grid, along with the steps to reproduce the issue (if they are different from the ones shared in the thread).
Kind Regards,
Keen Software House: QA Department
Hello, Daniel!
Thank you for writing to us.
We tried to replicate the issue following the steps you shared, and the light did turn ON/OFF even when changing the Piston Max Distance to 5m.
Since the issue didn't occur on our end, could you kindly share further information with us? Did you experience this issue on a modded world/server (with active MODs/Scripts) or a vanilla world/server (without any active MODs/Scripts)?
If the issue occurred in a modded world/server, please create a blueprint of your affected grid, paste it in a vanilla world/server, and check if the issue still persists. If it doesn't, the issue you experienced might be caused by the MODs/Scripts.
However, if the issue still persists in a vanilla world/server, please send us a screen recording/video showing the issue and the blueprint of the affected grid, along with the steps to reproduce the issue (if they are different from the ones shared in the thread).
Kind Regards,
Keen Software House: QA Department
Hello Engineer,
as there has been no reply to this thread in some time, we will close it. If you're experiencing this issue, please create a new thread.
Kind regards,
Keen Software House: QA Department
Hello Engineer,
as there has been no reply to this thread in some time, we will close it. If you're experiencing this issue, please create a new thread.
Kind regards,
Keen Software House: QA Department
Replies have been locked on this page!