Conditions should have a variety of ways of ending about dm HOT 6 CLOSED

The creature id has to be stored as the creature's name. You can't store it's initiative order, because that could change before the end of combat.

from dm.

This will also required checking conditions for all creatures at the start and end of every creature's turn. It makes sense at that point to store the conditions globally, at least for ending them. But it still makes sense to store them locally for displaying creatures. However, creatures do not have a link back to the interface, and I don't want to add one to facilitate storing conditions.

But we will have to change storage. Do I want to change away from a dict? You could get stunned from two sources, and you would want to track those separately. So switch to a list of lists, rebuild it as you check it.

from dm.

Before moving forward, also consider changes to the con and uncon commands, think about how to handle the kill command, and specify changes to the update_conditons signature.

from dm.

Conditions do not necessarily stop when the source of them is killed. So leave that up to the user with uncon. I think the changes to the commands and signature are pretty obvious based on the syntax proposed in the first comment.

from dm.

Note that I will need to deal with groups as well.

Edit: No, that is all handled in get creature. But this is perhaps another issue. If one creature in a group has a condition, how is the DM/user made aware of that? Created issue #19 to deal with this.

from dm.

For the interface, I'm thinking dN to signify the duration of the condition. So d2 would last 2 rounds. Start and end can be handled as is, and anything else can be assumed to be the round it is checked.

from dm.