Arissana should lock out the corp from rezzing ICE until priority is passed during runs

[izzystardust]

Same as Masterwork - it's really easy for the corp player to forget you have priority in the PAW and to snap-rez their ice, which is basically impossible to fix since you learn what the ice is if they rez it.

[TreffnonX]

Same goes for installing Picachao on the approached ICE, as it has to be installed before the Corp has the change to not do anything (including not rezzing the ICE), which will make Arissana miss her chance to install it to still make use of it this run. If the Corp already clicks "don't rez", the UI will tell so in the log, and the runner gains the info they need before actually installing. After ICE is rezzed, however, the PAW needs to go back to the runner (after Corps yields it).

I feel like "fixing" this goes along the lines of a checkbox in the UI that says: "Merge PAW Priority". If that checkbox is active, PAWs behave as they currently do in Jnet: Both players can act "simultaneously". However, if only one player unchecks the box, it should go to an active Pass-Priority pattern in which the player with the current priority must actively yield it to continue. This could also help with the ever-troublesome Self-Modifying Code/Simulchip into Clot and similar issues that arise from priority windows being stepped over too fast or being done out of order.

This would impact the game fluidity however. Maybe it should be an active "insist on PAW" after any click, instead of the "please pause", that would request priority and stop the other player from taking actions that require a click, therefore stopping them from doing those, before the other player yielded priority back, but only for the next PAW.

[NBKelly]

Right now we don't even have paid ability windows. Sooner or later, when I implement those, this will just naturally be a feature.

For now, you just need to make sure you and your opponent are on the same page at some point during the game.