if you want to make it disappear from the git history entirely, use git reset --hard HEAD~1 (normally not recommended if people have cloned your branch, which no one has done so far)
otherwise, just undo the changes and make a new commit
> Determines the creature type of the card. The available types are explained below. If you wish for a new creature type to be created, please create a new issue and mark it with the "mod" label. Please be as specific as possible as to exactly how you want the new creature type to behave.
technically, there's nothing preventing modders today from adding new creature types simply by changing the string
> adding a new creature type is as easy as changing the string attribute. No need to create a new issue (unless you have a feature request for a specific ability that those creatures should have and don't know how to create the systems to implement that)
So @Simon... clarification... right now, the cards say creature: "Bio or whatever. According to your last chat comment, it should be creature: true, creatureType: "Bio"?
> Apparently it is possible to have a creature with `-5` health in play. It isn't removed until it is dealt damage by something. This is not as it should be. Whenever a creature has -5 or less health, it should be removed.
Possibly use a form of `State-based actions` (MTG term) to scan for stuff like this
@Phrancis This is not a problem... you should just pull before making any change... since source control is exactly made for that : commits from two different sources... ;)
> It feels like these JSDocs really don't explain much... and keywords.cards.set is not a boolean, it is an object containing further information about what to set (resource and value).
@SimonAndréForsberg Probably, could be that something was just overlooked. I'm guessing if attack: 0 is set, it should probably have noAttack: true as well right?
