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]: Configure token size categories #4849

Open
Baaaaaz opened this issue Jun 29, 2024 · 0 comments
Open

[Feature]: Configure token size categories #4849

Baaaaaz opened this issue Jun 29, 2024 · 0 comments
Labels
feature Adding functionality that adds value

Comments

@Baaaaaz
Copy link

Baaaaaz commented Jun 29, 2024

Describe the Problem

MapTool has no functionality enabling a GM to customise or configure token size categories.

  • currently token size names for a square/iso grid are seemingly named after D&D 3.0 sizes, gridless uses numbers, and hex uses a fraction or a name. Ref: https://wiki.rptools.info/index.php/token_Size
  • game systems are likely to use different size names or have a different number of size categories entirely but MapTool does not support size customisation leading to a disconnect between MapTool sizes and the games system sizes.

The Solution you'd like

  1. Similar to other items under Campaign Properties, as a GM I'd like to be able to configure, save, export, and import token sizes to suit my game system of choice, such as the ability to:
  • rename a size rather than being forced to use numbers (gridless), D&D 3.0 size names (grid/iso), or a mixture of fractions/names (hex) in both MapTool GUI and MT Script.
  • set a display name to be shown in the MapTool token context menu size item (if different to the size name)
  • change a size scale, e.g. Colossal from 1.0 (6x6) to 1.0 (8x8), or Fine from 0.5 to 0.25
  • add new sizes, e.g. adding a grid/iso size 'Big' with a scale of 1.5 between 'Medium' and 'Large'
  • remove/hide redundant sizes so they do not show under the MapTool token context menu size item
  • delete sizes
  1. MT Script functions to support relevant features above. e.g. adding campaign size values to getInfo("campaign") results.

  2. When importing predefined Campaign Properties (e.g. Dungeons and Dragons: 5th Edition), set the sizes correctly for that system.

Alternatives that you've considered.

  1. Having some data mapping residing somewhere in the campaign file that can translate the game system size into MapTool size, but then the sizes show in the MapTool GUI still use MapTool sizes.

Additional Context

D&D 3.0 came out in 2000, so MapTool needs to get with the times and size up supporting sizes from other games systems! e.g.

@Baaaaaz Baaaaaz added the feature Adding functionality that adds value label Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding functionality that adds value
Projects
None yet
Development

No branches or pull requests

1 participant