You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Judging by the speed of things updating, it seems that if you haven't clicked on the Hyper button at all, it will be in Hyper mode. If you click on it once, it will disable it silently. This is bizarre and means most new players have played on Hyper without knowing. Also, Hyper doesn't change the rate at which wood and traps can be reharvested. (Correction: It doesn't change the speed of the cooldown once it's already started.)
EDIT: I have found part of the issue. In engine.js it has doubletime = true under options, but it doesn't update the buttons at the bottom to say Classic. So I can only assume the developers thought at least the start of the game was too slow without Hyper mode, but they forgot to update the bar at the bottom if Hyper mode hasn't been DELIBERATELY turned on. And what's more, if you turn Hyper mode OFF deliberately then quit the game, on restarting it will be secretly on again (as it defaults to on and nothing turns it off upon starting a game where hyperMode = "false" or not set).
If someone does deliberately turn it on, it will be OFF during your next session because it defaults to on, but because it's trying to turn it on, it ends up turning it off. So the whole feature is completely broken.
To be honest most people probably prefer Hyper mode anyway, but it would be good to at least have an accurate GUI. I honestly don't know how to solve this for everyone but I'd probably say default it to on but make sure that turning it off is saved and remembered correctly.
EDIT 2: Also, if it's off and you get into an encounter, turning it on mid-encounter will not speed up the current enemy's attacking but it will halve your attack cooldowns, making the game easier.
The text was updated successfully, but these errors were encountered:
There's still the problem that changing it doesn't affect current cooldowns, and (I think) doesn't change the speed of an enemy attacking if you change it mid-battle. Turning it on after doing wood and traps means waiting longer before being able to do wood and traps again, and turning it off after doing them means a faster cooldown for that time.
Judging by the speed of things updating, it seems that if you haven't clicked on the Hyper button at all, it will be in Hyper mode. If you click on it once, it will disable it silently. This is bizarre and means most new players have played on Hyper without knowing. Also, Hyper doesn't change the rate at which wood and traps can be reharvested. (Correction: It doesn't change the speed of the cooldown once it's already started.)
EDIT: I have found part of the issue. In engine.js it has doubletime = true under options, but it doesn't update the buttons at the bottom to say Classic. So I can only assume the developers thought at least the start of the game was too slow without Hyper mode, but they forgot to update the bar at the bottom if Hyper mode hasn't been DELIBERATELY turned on. And what's more, if you turn Hyper mode OFF deliberately then quit the game, on restarting it will be secretly on again (as it defaults to on and nothing turns it off upon starting a game where hyperMode = "false" or not set).
If someone does deliberately turn it on, it will be OFF during your next session because it defaults to on, but because it's trying to turn it on, it ends up turning it off. So the whole feature is completely broken.
To be honest most people probably prefer Hyper mode anyway, but it would be good to at least have an accurate GUI. I honestly don't know how to solve this for everyone but I'd probably say default it to on but make sure that turning it off is saved and remembered correctly.
EDIT 2: Also, if it's off and you get into an encounter, turning it on mid-encounter will not speed up the current enemy's attacking but it will halve your attack cooldowns, making the game easier.
The text was updated successfully, but these errors were encountered: