Jump to content
General Bug Report Guidelines - Please Read ×
Echoes of Duviri: Share Bug Reports and Feedback Here! ×

Action Button (Default 'x') Shouldn't Be Un-Assingable


Niavlys77
 Share

Recommended Posts

So a friend of mine tried Warframe for the first time on the weekend. He wanted to assign 'X' to something without realizing it was used for anything. First issue here: the action button should NEVER be unassigned upon confirming changes to key-mapping. This shouldn't happen, and same with many other commands.

 

When he went to play his first game, hacking terminals, lockers, datamasses, etc all couldn't be used - he spent quite some time trying to figure out the "mini-game" haha. I'm not sure what exactly was displayed, but he said it listed a bunch of random letters to be pressed. I'll try to get a screenshot, but no guarantees. Second issue here: player has no idea that the key is unassigned - if you simply cannot unassign the action in the first place, this wouldn't be a problem.

 

- TL;DR -

Game says to press all kinds of buttons instead of "Action Button Unassigned".

Don't let players confirm key-mapping if certain keys are unassigned, and tell them which ones are required/missing.

Edited by Niavlys77
Link to comment
Share on other sites

You can edit control settings in game, so I view this change as unnecessary.

Why does that matter? When a new player changes it without knowing, they won't necessarily know what key it might be in the first place, or even that a key isn't assigned.

 

The biggest issue is the fact that this new player thought the game just sucked and made no sense. He didn't have the slightest clue that it was caused by a key being unassigned.

 

If you can't unassign a key in the first place, everything here would be resolved.

Edited by Niavlys77
Link to comment
Share on other sites

Why does that matter? When a new player changes it without knowing, they won't necessarily know what key it might be in the first place, or even that a key isn't assigned.

 

The biggest issue is the fact that this new player thought the game just sucked and made no sense. He didn't have the slightest clue that it was caused by a key being unassigned.

 

The game doesn't have that many controls. If they are in the key assignment menu, they can be bothered to spend 15 seconds reading what the controls do before they start reassigning stuff willy-nilly.

Link to comment
Share on other sites

The game doesn't have that many controls. If they are in the key assignment menu, they can be bothered to spend 15 seconds reading what the controls do before they start reassigning stuff willy-nilly.

Again - the game doesn't make it clear that it's a problem with a key assignment.

 

It tells him to press buttons. All kinds of random ones. Try unassigning it yourself to see. I'd try it myself if I were at my home computer.

Edited by Niavlys77
Link to comment
Share on other sites

Hang on, the game DOESN'T warn you about an unbound key? I mean I've half a brain, so I never tried running with an unbound key, but it absolutely should warn you about it.

I haven't tested myself yet, but apparently this is the case.

 

For a new player who wants to change keys without thinking first, this is definitely an issue. Also, it's pretty easy to accidentally set a key to one that was set elsewhere, but AFAIK, it doesn't tell the player about replacing the other mapping.

Edited by Niavlys77
Link to comment
Share on other sites

Again - the game doesn't make it clear that it's a problem with a key assignment.

 

It tells him to press buttons. All kinds of random ones. Try unassigning it yourself to see. I'd try it myself if I were at my home computer.

 

I agree that the game should never provide misleading information like random strings where there is supposed to be a prompt to press a key. That is pretty clearly a bug, but this is a distinct issue from the ability to leave keys unassigned.

Link to comment
Share on other sites

I agree that the game should never provide misleading information like random strings where there is supposed to be a prompt to press a key. That is pretty clearly a bug, but this is a distinct issue from the ability to leave keys unassigned.

Different issue - sure. But not letting the key be unassigned in the first place would completely resolve it, since this issue simply could not occur.

 

On a side note - forgot to test and screenshot...will have to remind myself to do it tonight.

Edited by Niavlys77
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...