Bouncyrock / TaleSpire-Beta-Public-Issue-Tracker

Issue tracker for the TaleSpire Beta
33 stars 17 forks source link

Multi-Select / Fog of War Bug #894

Open Galeteya opened 3 years ago

Galeteya commented 3 years ago

Describe the bug The Fog of War hotkey sets to "LMB" by default upon launch of a new instance of TaleSpire, causing it to appear when attempting to multi-select.

To Reproduce Steps to reproduce the behavior:

  1. Launch TaleSpire
  2. Look at settings to see "LMB" being set for adding Fog of War
  3. Try multi-selecting.

Additional context There have been a very large number of topics discussing 'big black boxes' that appear when trying to copy/paste or multiselect, and the answer is always the same of 'accidentally setting the hotkey to LMB' where the person with the bug will go in, see - sure enough - the hotkey is set incorrectly, and figure they just did it by mistake. However, to ensure I wasn't crazy, I continued to reset the hotkeys specifically and close the game to relaunch it. Each and every time it's reset the hotkey of adding Fog of War to "LMB".

Additional reports: https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/757 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/740 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/737 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/778 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/735 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/812 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/826 https://github.com/Bouncyrock/TaleSpire-Beta-Public-Issue-Tracker/issues/866

Again, this is not an accident on the user's part. This seems to be a bug that continuously sets "LMB" as the default hotkey for adding Fog of War upon launch.

LuPro commented 3 years ago

I'm fairly certain there has to be more to this, otherwise more people would be seeing this issue. All the reports back then that you linked probably were connected to a different bug where when you accidentally click on the menu (like when going through the settings to see what's possible to change) the game wouldn't stop "reading" for a button input to set the values to even if the menu was closed so setting a left click on accident without knowing was very easy. This has been fixed since then (and it's evident that this was the main cause of the problem as the reports went from several per day to almost none with that patch) and additionally the devs added a lock so the fog of war button mapping can't be a mouse button anymore - but this is where the new issue arises. Theoretically it should be impossible now to have the fog of war bound to the left mouse button, yet you had it and it reset to that button on restart, which is very odd. I may play around with it later in the evening and check if I can reproduce it, but I'm fairly certain there's more steps to it than just restarting.

Galeteya commented 3 years ago

Theoretically it should be impossible now to have the fog of war bound to the left mouse button, yet you had it and it reset to that button on restart, which is very odd. I may play around with it later in the evening and check if I can reproduce it, but I'm fairly certain there's more steps to it than just restarting.

Unfortunately for me, it is just restarting. Thought that may be a symptom and not the cause. I'll address both the add and remove (which has no bound hotkey by default) Fog of War, exit the menu, reopen the menu and ensure they still remain and are saved/cached, and close the instance. Upon launching a new instance, it's set right back to "LMB" for adding.

LuPro commented 3 years ago

Maybe it gets triggered by setting a keybind and removing it? as in the game remembers that there was some keybind but since it doesn't exist anymore it just sets something which happens to be LMB? Edit: Does it also reset to LMB if you set it to something else and restart, or just when the keybind is left empty?

Galeteya commented 3 years ago

Unlikely since the default keybind that gets replaced for removing FoW is null.

hailiedrescher commented 3 years ago

Mine is defaulting to "ctrl" and "alt" for show and remove FOG and trying to set it to even number keys (i was using 8 & 9) it wipes that on reboot.

Galeteya commented 3 years ago

That's interesting. I was binding mine to + and - on the numpad. While there shouldn't be any case at all in regards to differentiating the 8 below function keys and 8 on a numpad, you didn't happen to bind them there did you? I'm grasping at straws here to try and find a connection xD.