Re: Community Wad
Posted: 27 Jun 2016, 22:32I'm not sure why Den Protector isn't working. I've checked the code and it appears it should be working. Could you test Aura Gnarlid? They have the exact same code. Make sure Aura Gnarlid isn't still a 1/1 and that the blocking creature doesn't have 0 power. If it doesn't work, then either there's something on your end interfering or all cards with that kind of ability will need fixed.Borborigmos wrote:Just managed to make a 19/18 Den Protector and it got blocked by a 4/4 and a 5/5 my opponent had in play.
On a different note, I'm trying to create my own double face cards but I can't seem to make them work. Could you please tell me the files that make double faced cards work (aside from D14_TFM_TRANSFORM.LOL)?
Thanks
----
That should be the only external file you need to change outside the cards themselves. They're kind of finicky, though.
Double faced cards suffer from a number of issues, and those issues are dealt with via some complicated but effective mechanics. Making sure everything is set up for those mechanics to handle properly isn't quite as self-evident as for normal cards, though.
At the beginning of the game, double faced cards need to spawn a token of the back face to store its copyable values for later in the game. In order to make sure the token isn't visible, the token is missing its types and subtypes. That's why the types and subtypes are supposed to go into the lol file.
There are 4 functions used at the beginning of the game on different cards. Any given card will use 2 of them. Either ("DoCardRegistration_Resolution1" and "DoCardRegistration_Resolution2") or ("DoCardRegistration_Resolution" and "DoCardRegistration_Resolution3"). The former pair was created by TFM to work with the method he'd come up with for making the token not visible. The latter pair was created by someone else and don't require that the token be missing types and subtypes to not show up. For the sake of consistency, all new DFCs will use the ones created by TFM, and that's what I'd suggest. However, there are still many cards in the CW that were made using the other 2 because I didn't know at the time that those two functions weren't originally part of the transform file. So, when choosing a DFC to copy, make sure it's got the 1 and 2 functions, not the others.
Bloodline Keeper//Lord of Lineage uses the right ones.
Aside from that, you'll need to make sure that the back face has a certain function called. Every back face of a card should have the code, it's got "TFM_Transform().ResetTransformation()" in an RTA.
The front face should only reference the back face in two locations. In the DoCardRegistration_Resolution1() function, it should call the filename. It should also have a token registration for the back face.
Finally, as was noted by others, the ArtID for the back face must be nothing but numbers. In some situations (such as if the front and back are different colors) you can use one with letters, but normally, it's parsed by a functions expecting a 32-bit signed integer, which means -2,147,483,648 through 2,147,483,647. I've been using negative numbers to keep back faced card images easily identifiable (while I use the card's name for front faces and normal cards).
Depending on the issue you're having, I might know how to fix it, though I can't guarantee anything. I messed around in the functions for DFC quite a bit, though, when I was making the last set.