Re: Card Creation Request Thread
It is possible that Moment of Heroism is in your opponent's deck (all cards in the game are processed and any card regardless of which player is using it). It is also possible that Moment of Heroism is showing up from previous games and you are just now noticing it.loookaz wrote:ok, i've found this in the script log:but i do not have Moment of heroism in my deck. what gives?
- Code: Select all
[lua] [string "MOMENT_OF_HEROISM_277046_TITLE (CONTINUOUS_ACTION) [1630]"]:2: attempt to index a nil value
[lua] [string "MOMENT_OF_HEROISM_277046_TITLE (CONTINUOUS_ACTION) [1629]"]:2: attempt to index a nil value
[lua]
i am starting to think that the crashing error might be somewhat connected to Crop Rotation, but i am still not certain:(
Of course it is always possible that what is causing the crash is not showing up in the script log because sometimes the first time the error occurs it is enough to crash the game (thus no entry in the script log because the game crashed before the log was written).
Unfortunately when tracking down crashes it is usually best to reduce the number of variables for example try any suspected cards by themselves in a deck that uses only pre-built or simple known good cards (sometimes you will need to run tests multiple times). Then if you can't reproduce the problem with any of the suspected cards by themselves start mixing them with the other suspected cards (starting off minimal like 2 suspected cards, if none of those combinations produce the crash then try combinations of 3, etc...) until you've tried all suspected cards. If you still haven't reproduced the crash then start adding the other originally non-suspected cards one at a time until you get the problem to reproduce. This is a very time consuming method, but it does usually produce results in figuring out what is bad or in what combinations is something bad.
There are two ways that I know of to prevent untapping.yinyangyan wrote:How would I go about making it so a creature does not untap? Trying to make Leaden Fists and that's all I'm missing, and I can't seem to think of any card that does that already.
- Use the characteristic, CHARACTERISTIC_DOESNT_UNTAP, to prevent untapping between end of turn and upkeep. (Note that this can be difficult to get right and could have issues mixing with other cards.)
- At end of turn check to see if the enchanted object is tapped and if it is call TapAndHold() on it to prevent it from untapping at next upkeep. If it is untapped then do nothing (as we don't want to tap it for no reason). This may have issues of it's own, but I believe this would work better as it should allow other cards/abilities to untap the enchanted object.