Tried it twice today, once for testings sake, twice for confirming the bug.
If you go to weapon mods and "Try" to see what a rune would do for your weapon without confirming the mod, the weapon gets modified and you lose the rune, even if you didn't want to use it, when you hit BACK button and "cancel" the modification
Posted here, since there is no "general" / bug submissions forums for MP (and to warn others)
Dunno if these bugs were "pre-patch 2", but these are some 'serious' bugs, specifically, since loot is RNG
I've never even noticed a "try" button.
Seems pointless.
You can go and "mod" your weapon, but it always asks you to VERIFY the modification before you proceed, there is a "yes i want to" and "no i don't want to" button.
And when you hit the "no i dont want to", the MP does it anyways (dunno if this happens in SP too, didn't happen pre-patch, that i'm sure of).
What's with the PSA all over titles?
Just tried this on the Xbox One again, and it doesn't consume the rune. I've done it several times in the past and never lost anything.
I've noticed this but I'm pretty sure it isn't asking you to verify. It is asking actually asking you to apply it anyway. Least, that is what I recall reading it as.
What? There's a TRY option? Is that like an Xbone exclusive because I've never seen that option. Why would you want to "try" to see the upgrade change when the upgrade window tells you what the rune does?
What? There's a TRY option? Is that like an Xbone exclusive because I've never seen that option. Why would you want to "try" to see the upgrade change when the upgrade window tells you what the rune does?
He's talking about hitting "Confirm changes" then backing out when it gives you one last chance.
Ooooh. The "problem" is that you are prompted a second time (when selecting B for Back) after backing out of the confirmation change. The rune is still slotted. He probably pressed A/Yes and confirmed the addition instead of stopping to read the dialog. What is should do is unslot the run after you denied the change the first time.
Is kind of like when web designers or programmers put in "Do you want keep this dialog open? Yes/No". The user's intent was to close the box in the first place and will instinctively or confusingly click Yes. Unless of course there actually is a bug, but I haven't come across it even though I've used that feature multiple times.
Retour en haut
