Skip to content
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

[Feature request] Ignore certain tokens from scattering #9

Open
gsterling opened this issue Jun 14, 2023 · 3 comments
Open

[Feature request] Ignore certain tokens from scattering #9

gsterling opened this issue Jun 14, 2023 · 3 comments

Comments

@gsterling
Copy link

My problem

I use tokens for chests, ladders, lights, etc. and I don't want them to move, when players walk over them.

Requests

  1. Would it be possible to add a toggle to the token configuration window, to disable scattering?
    Let's say I have 3 token in a square. If one of them is a ladder, I don't want it to be taken into account when calculating and rendering the scattering. So it should look as if there are the other 2 token on the same field and the ladder should stay in the background.

  2. Could you also change it to still be taken into acccount on mouse over?
    So the disabled tokens are only scattered with the rest of the tokens when the mouse is moved over the square.

  3. Also can tokens be scattered according to who is eligible to move the token?
    The players won't be able to move the ladder on their own, that's something the gamemaster has to do, so they won't need to see the ladder in the scatter, but the GM might want to move it away from under the other tokens and therefore would need to have it scattered.

Possible configuration options

It could look as simple as this:
image

I propose the following:
Z Scatter In background [ ] On mouse-over [ ] Only owner [ ]

  • In background would disable scattering and always put the token behind everything else that has scattering enabled.
  • On mouse-over would only be clickable when In background is active and would add the token to the scatter when the mouse moves over the square.
  • Only owner would only be clickable when In background is active and would only scatter the token for the token owner (and GM, so basically everyone allowed to move the token).

Examples for all cases:

  • Normal - Nothing is selected. Default. Everything works like it does now.
  • Light object - Only In background is selected. The light should always stay in the background, won't be moved (after being placed) and won't be targeted or interacted with
  • Treasure chest - In background and On mouse-over are selected. The chest should not move when players walk over it, but should still be interactable and therefore should be scattered when the player's mouse moves over the square
  • Ladder - In background, On mouse-over and Only owner are selected. The ladder should in all circumstances stay in the background for the player, since they aren't able to move it and it's basically a map feature for them. The GM however want's to move it and needs to be able to select it, so it should be able to scatter.
  • Mounts or companions - In background and Only owner are selected. The token should always stay in the background, but still be visible for the owner of the token at all times.

Since On mouse-over and Only owner only reenable scattering in certain cases, it won't be necessary to allow them, without In background.

@SirGarhi
Copy link

In a similar vein, I would love to see an option to have dead creatures not contribute to scattering. In our group we use bloodsplats to replace dead creatures but leave the token on the map, and it would be awesome if the blood splatters didn't force tokens to scatter out of the square.

@elizeuangelo
Copy link
Owner

A very easy way to accomplish this is shift-clicking and slightly moving the token (could as little as one pixel).

@Michael-B-23
Copy link

Thirded. We use "Ridable" as one of my player's is a goblin who mounts a wolf. I would love to have a way to not have them scatter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants