-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Familiars jump around and do not get smaller #85
Comments
I can currently not replicate the behaviour you described for familiars. Trying it in a test environment as you mentioned would be quite helpful, i would suggest trying to see if it also happens in a new empty world and using Find the Culprit. Besides that, could you send me screenshots of your Rideable world settings and of the ridden tokens Rideable settings? |
oh, I haven't touched the on token riders scale, its still set to 1 |
Ahh, sorry i wanted to mention the part with the familiar scaling in my last answer, i just forgot. The problem with the scaling is, that foundry only allows for certain token sizes. I assume you familiar has a size of 0.5x0.5? This is as far as i know the smallest possible size for tokens. I plan on adding a purely visual scaling option in a later update though. That the offset does not affect familiars is intentional. |
I will look into adding a setting to enable the offset for familiar riders with the next update. |
I was playing with this mod the other night.
LOVE THE IDEA!
we enabled Familiars so the mages can have their cats ride on their shoulder.
when they walk around it seems like the familiar often gets lost in the walls and bounces around or detaches.
have you seen this before?
I also have the size change when riding enabled and set to .6, and it doesn't seem to work with familiars?
have not played with trying to make a horse or wagon yet.
we are using the ARS game system and V12. I do have several other plugins running but nothing that effects tokens that I'm aware of. later this week I hope to try things in a test environment to help narrow down possible issues there...
The text was updated successfully, but these errors were encountered: