Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Curse of Strahd Module Tokens Not Working

I recently purchased the curse of strahd module to transfer my campaign over to an online format due to the spread of coronavirus. I'm getting the hang of roll20 over all but when I pull a monster (the revenant, specifically) from the journal over to the playing field nothing happens. I'm opening the bio page and then trying to pull the token from there, and it seems to work for some monsters but a majority of them don't work. 
I'm having the exact same issue. It works for some but not most. The NPCs seem ok but not the monsters. When I try to drag the token from the bio page it seems like it fails to grab anything.
Hi Alex! I've worked out that it's because each character's default token field is filled with a blank token. Not no token, some form of null token, so it doesn't get placed. Fortunately, I have a solution, but it is a bit of work. Most of the entries in the journal have a token already placed on one of the various maps. So I went through each map (page), selected a placed token, searched for its counter part in the journal, opened, clicked edit, removed the blank default token and then clicked on use selected token. Then clicked save as. This has fixed the issue for me for all placed the tokens that I could find, which is most of them. However, monsters and NPCs that exist only in Castle Ravenloft don't appear to be placed anywhere. Strahd is ok because you can spawn his token from the rollable tokens section in the collection tab, then do the same as above. For monsters that also appear in the compendium you can delete their entry in the journal then it will allow you to drag the compendium version in, which will place a character for it at the top of the journal. We may have to work out a more manual process for unique NPCs and monsters that can't be fixed by any of the above methods, such as Rahadin.
1585576276
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
That doesn't sound right. The monsters should be ready to go, tokens and all and should not require any  post-processing steps like that. The original issue sounded like it was just a matter of trying to place a monster by grabbing the handle in the journal entry instead of the name. The handle is the three little bars next to the name and  is used for changing the order of journal entries. To drag and drop a creature, you must grab it by the name. If the game you are using requires the steps outlined above, it sounds like the game is corrupted somehow. Try spawning another copy and see if you have the same issue.
1585606740

Edited 1585606837
Thanks for the reply! I did read other threads about people dragging the wrong part of the journal entry. I definitely made sure that I was dragging by the name and not by the handle on the side. I am able to drag and drop characters that I create and provide tokens for, so I know that I am clicking and dragging the right thing. I also tried to create a new game using the same module and got the same results. None of the tokens in the journal are drag and droppable, and appear to just have a blank white square in the default token field. Like there is something there, as you can press the remove button, but it doesn't correspond to anything on the board. I agree it's quite strange, and I agree that no post work should be required. And yet...  I'll see if I can get a log. Or maybe a screen grab of what the monster entry looks like.
Ok, I've worked out more. I've been using the Castle Ravenloft map pack add-on. I created a new game without the add-on, and the token problem did not appear. Each monster and NPC in the journal drags into the play area fine. I exited the game, and added the Ravenloft add-on, and re-launched the game. The problem now appears. It has something to do with the add-on.