Re: Bug Reports (snapshot builds)
Posted: 28 Mar 2019, 02:51
You shouldn't need AltImages anymore. The way tokens work now, is that they are defined in several places:AStrangerIsHere wrote:1.6.23-SNAPSHOT-r196-51e9e2b692
The new token system is not really working, or should I say not for all cards. Tokens created with History of Benalia doesn't display any pictures IF I name them w_2_2_knight_vigilance_dom. But without the _dom at the end, it works. But the script (?) for the card is:And there's a question I would liked to ask: is it still possible to display different pictures for the same token? In the past, I would modify a card by adding TokenAltImages$ w 2 2 knight dom2 for example. Does that still work?SVar:DBToken:DB$ Token | TokenAmount$ 1 | TokenScript$ w_2_2_knight_vigilance | TokenOwner$ You | LegacyImage$ w 2 2 knight vigilance dom | SpellDescription$ Create a 2/2 white Knight creature token with vigilance.
Edit: ok, it still works BUT only without the _dom at the end of the name, so now it's TokenAltImages$ w 2 2 knight vigilance2, at least for History of Benalia. I have to try for the other cards.
1) As a token script
2) In the editions file that produces that token
For tokens that have multiple images, multiple instances of the normalized name "w_2_2_knight_vigilance" should appear in the editions file. So in the Dominaria editions file, you see two instances of that and 3 instances of Saprolings. Based on the edition,
So I tried your exact test case with the auto-downloader on and it decided to try to load:
Forge\Cache\pics\tokens\w_2_2_knight_vigilance2_dom.jpg
Forge will randomly decide based on the token + edition which file to load. I'm guessing when you were trying it, you didn't have anything in place for both:
w_2_2_knight_vigilance_dom.jpg
w_2_2_knight_vigilance2_dom.jpg
The reason it works without the dom is that's Forge's general pattern for all images. First try for the edition specific image, then the non-edition specific image. In the future where specific cards generate specific image tokens, we'll have a mapping in place so it doesn't just randomly grab from everything.