search

zeel01 / roll-tokens

A foundry VTT module to randomize and control the image and name of a Token using a Rollable table.
MIT License
4 stars 2 forks source link

V10 Issues #5

Open InstantZzz opened 1 year ago

InstantZzz commented 1 year ago

Hello, I am having issues with this module with V10 for Foundry. More specifically; V10.288. I have tested the module in Pathfinder 2E V4.2.6 & Call of Cthulhu 7E V0.9.2 The Pathfinder test included multiple modules as that is a game I currently running and I tested in Call with just this single module. I have the same issues in both game.

I've gone through process to create the rollable-table as is described on the module page and linked it to one of my NPCs. The issue I am having is that when I go to Token Image Selection, regardless of what I pick, the image does not change.

Also - I am not sure if this is bug but I found it odd; when I use the randomizer, the token does change but it also locks that option and I cannot roll that option on any token currently on the map or any new token that I create, without opening up the table and unlocking that result. I say that I am unsure if this is bug because I normally use the selector and do not know if the randomizer is working as intended.

jax7778 commented 1 year ago

I am having the same issue, I think this add on is probably no longer maintained. hopefully we can find a substitute, or the developer will pick it back up

*Edit, combining this module: (Which is in the registry) https://github.com/TheNekoMomo/Momos-Token-Changer

With Wildcard tokens, you get the ability to choose the wildcard face. That is pretty much what I was using this for. So it works for me.

wsethbrown commented 1 year ago

The error is Error: You are accessing the TableResult#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.

I haven't made any foundry modules yet, but this seems like a fairly easy fix.

EDIT: I've been told this warning is likely not causing the module to stop functioning.