[Feature]: Draw tokens based on available light/the token's visibility/the observer's senses

Open
  • Is something wrong?
#6,024 1 comment 3 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
computer-graphics, desktop, game-dev

Research direction

This is a design-level rendering change, not a first patch: tokens should look different per observer based on light, concealment, and senses (greyscale darkvision, brightness for dim light, false colour, outline, blur). Start from the linked issues #4379, #4836 and #3347 and from how tokens and lighting are drawn today. Done means per-viewer appearance plus accessibility prefs so hover labels and sheets do not undo the effect. No files or tests are named in the issue.

Written by the indexing model from the issue text.

Description

feature
Describe the Problem

Similarly there are systems like Pathfinder which have the concept of being generally aware of a creature without being able to see them clearly.
Presently a tokens appears the same regardless of how well they are illuminated or if they are supposed to be unclear.

The Solution you'd like

It would be nice if tokens were rendered with regard to how they should be perceived.
Ideally this would account for the variety of perceptual senses available in various systems;

  • Dark Vision is commonly supposed to be monochrome (apply a greyscale filter),
  • Dimly lit (adjust image brightness/contrast),
  • Different spectrum vision - e.g. IR, UV, N-Ray (apply a false colour filter),
  • Concealed/Obfuscated (draw an outline)
  • Unclear senses like hearing and tremor sense (blur the image)
  • etc.

Consideration would need to be given to pop-ups. If something is supposedly obscured but you can just hover the mouse over the token and read the label or see it clearly on the attribute sheet the effect is somewhat nerfed.

There are accessibility concerns since we are deliberately messing with the ability to see things. Painting a token with reduced brightness will impact some users more than others. User preferences should include options for altering the method employed.

Alternatives that you've considered.

Token opacity can be applied for some circumstances like invisibility, but it affects all viewers the same. A token with the ability to see invisible does not get an improved view.

Additional Context

#4379
#4836
#3347

Dominant language
Java
Stars
927
Forks
286
Avg merge
3d 17h
Merged PRs (30d)
94

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RPTools/maptool

All issues in RPTools/maptool

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.