Changing initiative order

Project:Virtual Combat Cards Project
Version:0.92.2
Component:Code
Category:feature request
Priority:normal
Assigned:Nebulorum
Status:closed
Description

Some way to change initiative order (without having to resort to delay) would be nice, there is at least one power that does this (guileful switch) and it is currently very difficult to implement.

#1

Assigned to:Anonymous» Nebulorum

After some consideration I believe the best way to solve this is to have a Initiative action to move a combatant to a position before some other combatant.

This should be restricted as follows:

  1. Active combatant can't move (since he should always be the first);
  2. You can't move a combatant You can't move combatant before an active combatant;

So Guileful Switch can be implemented with the following actions (say the order is: W,Nw,...,A,Na,..,L):

  1. Warlord(W) uses power, you "Move Ally(A) before Nw" (Sequence: W,A,Nw,...,Na,..,L);
  2. End Warlord round Sequence: A,Nw,...,Na,..,L,W);
  3. Move Warlord before Na (the one that was before the ally) (sequence: A,Nw,...,W,Na,..,L);

#2

Implemented a "Move Before" action. Not very happy with the controls. If nothing changes it's due to the fact that the operation is invalid (see condition on comment #1). Comments on improvements are welcome.

#3

This worked without a hitch in my game last night. The controls are a little clunky, but it is a situation that typically only comes up 1x per encounter, so no big deal. Much thanks on this tweak! Keep up the awesome work!

Ed P.

#4

Status:active» patch (ready to commit)

I know it's a bit awkward. As you move the combatants around you kind of loose order. The ideal solution would be have some kind of Macro for this operation. But this requires some thought and design. I improved the design a bit, so that now the check box is more obvious.

#5

Status:patch (ready to commit)» fixed

Implemented on version 0.92.3.

#6

0.92.3's layout for this action is much better. Thanks!

#7

Status:fixed» closed

Automatically closed -- issue fixed for two weeks with no activity.