dorpond wrote:I think what bothers me the most about InitTool is that all the condition timers are on the top of the list.
Actually all timers are shown in order of initiative. They work this way so that the GM can apply effects to creatures as needed. Take Melfs Acid arrow for instance, you need to apply the damage to the affected creature every round. But even if the caster or the target delay in some later round, the acid damage still gets applied at the same point in the initiative. So I've set it up so that timers show up just above the current creature (if nothing else is selected) at the same initiative. When the next round occurs, the GM knows exactly when to apply the damage.
Sometimes the GM doesn't need to know when the item shows up in the initiative. The bless spell is a perfect example, you apply the bonuses from it when it is cast and then forget about it until the bonuses expire. That is why there is a 'Reminder' timer type. It doesn't normally show up in the encounter until the spell's duration expires. When it pop's up, the GM can tell everybody they are no longer blessed.
The point I am trying to make is that timers actually become a part of the encounter, not just attached to creatures in the encounter. They have an initiative that can be different from their caster's and their targets' initiatives.
dorpond wrote:If conditions were layed out like a subdirectory under the players in the list, it might be easier.
I understand what you are saying about a tree structure, but wouldn't this info be shown in the index card idea that you told me about above? If so, then you wouldn't really need the tree at all, would you? Or am I misunderstanding what the problem is?
