Cannot reset Block selection by Reselecting it.

Suicide Neil shared this bug 23 months ago
Reported – Awaiting fix

As title, since the most recent update we can no longer reset the block selection ( blocks with sub-types or different options/shapes ) simply by selecting it again from the hotbar.

Fix please.

Comments (3)

photo
1

Bump- just checked, still not fixed.

photo
1

Hello Neil!

Could I just clarify this one? Do you mean, for example, equipping a light armor block, cycling through to a sloped light armor block and clicking the armor block in your hot bar again (which will give you the small grid option) Or, do you mean equipping a light armor block, cycling through to the sloped armor block, selecting another item altogether and then coming back to the armor block which is still showing as sloped?

Kind Regards

Laura, QA Department

photo
1

"equipping a light armor block, cycling through to a sloped light armor block and clicking the armor block in your hot bar again (which will give you the small grid option)"

That one, yes. It used to be that clicking the block on the hotbar would reset the block to the first shape/option it has when you were building with it, regardless being large or small grid that was selected.

photo
photo
2

Hello Neil!

Thank you for the information. I have reproduced and reported this issue.

Kind Regards

Laura, QA Department

photo
1

Hi Laura.

IMO clicking the hotbar button again should ONLY change the grid size, (or only reset the block group, which would require an alternate control for changing grid size), not both. 1 action per input.

Binding both actions to the same input is likely to cause confusion/frustration.

photo
1

Quiet, you.

I don't believe it would cause confusion at all- it didn't for ~5+ years, so why would it now? More to the point though, if someone wanted to reset the block to the first option, then clicking twice ( reset block + reset size back to what it was ) is far less annoying than having to scroll through half a dozen different block options to find the first one again.

photo
1

It's basic SRP/UX, you shouldn't have 2 (or more) competing actions/behaviours for the same input, unless they can be seperated contextually. Both actions are acting on the block selection within the same context (building mode) and therefore should have seperate inputs.


There is a third behaviour that interacts with this, the auto-changing of the selected block grid size when touching an other-sized grid, which could leave users clicking/scrolling multiple times to get the selection that they want.


And a 4th potential behaviour is the hotbar 'remembering' the block group selection between uses (mostly, it's broken for some 2x1 blocks). Resetting every time you switch block shapes would be frustrating.


The whole thing needs a fresh UI/UX pass since Build Planner, etc changes.

photo
1

The auto-changing block size when holding a selected block against an already existing grid will not cause confusion- it literally negates your argument about it being difficult for 'inexperienced builders' to select the desired sized block as the game does it for them. The moment they reselect a block to get the first option, the game will resize it for them too as they try to place it- or it gives a simple message on screen that it isn't available for that grid size.

Like I said though, it was never an issue for 5+ years and only got changed accidently during an update, putting it back the way it was would be far more preferable to most players in my opinion.

photo
1

I could as equally argue that it has been this way for nearly 2 years now, so why change it back? I could also argue that your report has 3 votes so why are Keen acting on it when there are more pressing bugs with higher votes?

This is why I say it needs a fresh UI/UX pass, probably taking into account why it was changed (it is not necessarily an accidental change as you state) and leaving aside personal opinions pro or con.

photo
1

1) because it was changed in error and needs correcting.

2) popularity contests are NOT the best way to decide which order bugs/issues get fixed in- the game is 7+ years old, when is a good time to fix 'less popular' reports?

3) They aren't going to completely overhaul the UI, as much as it may need it- it is functional, and clean enough, it just has enough quirks that it takes getting used to. The blasted P-button issue is the biggest complaint that needs addressing with the UI scheme ( and yes, it was changed by mistake- unless Marek is being a sadist again ).


I HAVE SPOKEN ಠ_ಠ

photo
1

1) Again, you don't know that it was an error. It may very well have been removed for a reason, which should be determined/reviewed before blindly taking action now.

2) Its not popularity, its frequency. Votes are supposed to represent more people indicating that they are affected by the same bug, although it's probably praiseworthy that Keen have got down to reviewing the 3pt reports :)

3) A UI/UX pass does not imply a complete overhaul, but it can indicate if changes are necessary, and should be a simple matter compared to making a blind change and having to deal with potential fallout from users.

The point of saying 'I could argue...' is to highlight that we can go back and forth on this, but fundamentally I believe it needs to be determined if it was an error, and if not, review the reason for the change before taking further action. Do you agree with that?

photo
1

1) if it was removed for a reason, then they surely would have mentioned it in the patch notes at the time. Oh, wait, keen don't do that for important things do they...

2) No, it's mainly popularity- issues are voted upon based on how well the person reporting it shares it around in order to garner votes. Important issues are easily buried in with the hundreds... thousands of other issues, minor and major and duplicates ( and non-issues due to inexperienced players not knowing how to play the game properly ). I have taught you well the art of snarkiness it would seem.

3) It's not a blind change, it's a considered one- tweakage of the UI is / should be easy enough, but like I said, we've been asking for changes for years...


We can certainly go back & forth on this all day, but the facts speak for themselves; 'it' was never an issue for 5+ years and should not have been changed, especially without any explanation or warning. I only agree with 'that'.

photo