Since September 5th, our players have started reporting that their fishing rods break and become unresponsive. The main script, which relies on the
touch_start
event, no longer triggers.
This issue resembles a stack/heap error, but in this case, no errors are reported by the simulator or viewer—unlike typical stack/heap failures. Memory exhaustion is also unlikely, as this script has functioned correctly for over 10 years without issues.
The problem occurs in the following scenarios:
* When players teleport between regions
* Occasionally during active fishing
* Some players report it happening upon login while they log in wearing the rod (as attachment)
The issue affects many players, but not all, which suggests that the problem is not caused by our scripts or the fishing rod itself. We have been unable to determine why the same fishing rod behaves differently: for some players it breaks, while for others it continues to function normally as it has for years.
Around 30 - 50 total players affected so far since September 5th.
Aprox. about 7% of our players have been affected.