kpruss wrote:Do you guys know anything about the AI values they put on the cards?
I'll tell you what I know by looking at other cards.
First, some score is automatically added to the cards according to how much each "standard" ability (like flying, vigilance, etc.) is worth, and other things (you can find all the default scores in DATA_CORE\DATA_ALL_PLATFORMS\CONFIGS\DEFAULT_AI_SETTINGS.XML). That score adds to the AI_BASE_SCORE that we write on the card, and lets the AI take decisions about "trades" (is it good for me to block that creature with this one if both die?), about which card should be destroyed when there's the chance, and so on. This, of course, has a meaning if we talk about the score of a card in play. When you define an AI_BASE_SCORE for ZONE_HAND, you are basically giving a score to what happens when you play that card, in fact you can see that kind of score on instants and sorceries, but also on permanent cards that have enter-the-battlefield effects. I think this also influences decisions made by the AI when choosing what to discard with
Duress or similar cards.
If you need to define a variable score, you can use AI_CUSTOM_SCORE (always defining the zone), make your math (for example you may want to raise the score of a card with threshold when you actually have threshold), and finally use Object():AddScore(...).
kpruss wrote:I found a sakura-tribe elder file, and it had AI value at like -450, which kinda threw me for a loop. The comp actually dislikes playing this card a lot, like it will always play nature's lore or rampant growth, which have zero ai value, (actually i think those cards don't even have that listed) but it would rather leave mana open to regenerate a troll 3 times than play this dude.
The -450 for
Sakura-Tribe Elder has a meaning if it's for ZONE_IN_PLAY because it's a creature that you don't mind if it dies (you would always sacrifice it in response). Maybe -450 is a bit exaggerated, I would give -150. Try adding another score for ZONE_HAND and set it to 450.
Your code for
Treetop Village should be mostly OK. I'd just suggest some improvements:
- Use EffectSource() instead of Object() inside the CONTINUOUS_ACTIONs of the activated ability, otherwise if the land gets killed when it is a creature, it will keep the transformation inside the graveyard until the end of turn, which isn't pleasant to see. EffectSource() gets cleaned when the card changes zone, Object() doesn't (in fact it's pointless to check if Object() ~= nil because Object() is never nil, while EffectSource() can be).
- Make the layer of the first CONTINUOUS_ACTION equal to "3" instead of "4" (original cards use "3" for changing types and "4" for changing sub-types).
- Remove the TOKEN_REGISTRATION since you aren't using mana tokens here.
Note that your land will have a colorless frame even if it produces green mana, but that can't be helped because card frames are decided automatically in DotP2013 with no overriding method (a decrease in quality from DotP2012). It will probably get the right frame when it is a creature because it becomes a green card.
Posted: 26 Nov 2012, 23:53
)
