Monday, 20th November 2017, 07:05 by crawlnoob
You are wearing ring A and ring B. You have a copy ring A2, which you do not know is cursed. You often swap ring A with some other rings, as ring B is a central piece of your defenses. However, you find yourself in a special situation where you should use both ring A and ring A2 at the same time. If you automatically swap ring A2 for ring B, and ring A2 is cursed, you can always swap ring A for ring B to get back to your original configurations. Only now your swapping ring is no longer removable.
Believe it or not, you can be in a game where the RNG does not give you remove curse scrolls for quite some time, or you use them up, etc.. The extra swapping also takes some turns, which could be life threatening if you happen to be doing this in a very dangerous situation. The optimal behavior is to swap ring A for ring A2 in a non-dangerous situation, to check for curses. Only with your proposal, the player no longer has this choice and has to force the situation by first removing ring B.
So the prompt for which ring to replace should still come up if the copy ring has never been worn. Once it has been worn, your proposal makes perfect sense. The fact that this exception is a less common occurance is an argument FOR including it, not the other way around. The player is not going to be bothered by the exception except in the rare cases where it may actually be important.
This is IMHO a very good argument for removing or heavily reworking the curse mechanic.