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

Cognitive Realm Layers #130

Open
1 task done
TheFlyingPig opened this issue Oct 29, 2024 · 6 comments
Open
1 task done

Cognitive Realm Layers #130

TheFlyingPig opened this issue Oct 29, 2024 · 6 comments
Labels
feature request New feature

Comments

@TheFlyingPig
Copy link

Is your feature request related to a problem? Please describe.
The cognitive realm is an important layer of reality in the Cosmere that certain abilities allow access to.

Describe the solution you'd like
The cognitive realm should be a map layer. "travelling to" or "visibility" of the cognitive realm just means taking the token into the related location in the Shadesmar layer upon a command/button press.

Describe alternatives you've considered
None

Version
0.1.1

Additional context
n/a

Checklist:

  • I have searched the existing issues to ensure this feature has not already been requested.
@TheFlyingPig TheFlyingPig added the feature request New feature label Oct 29, 2024
@Doc-Sun
Copy link

Doc-Sun commented Oct 29, 2024

Is this going to require a secondary map image for every scene? or is there a proposed place holder for any maps that don't have shadesmar? An inverter of some sort? especially with relation to the sea of beads in Stormlight.

@stanavdb
Copy link
Collaborator

I want to give some push back on this idea from three points:

  1. It will bloat GM prep, every map suddenly becomes two maps if you want to use the feature (even if there's only a couple of things in it)
  2. This is fundamentally not how layers work in foundry scenes and is not something trivial to implement. Different object types are on different canvas layers (tokens on the tokens layer, background on the background layer, etc.). What you want you want is essentially a second layer stack beside the first.
  3. The cognitive realm is a cosmere concept and doesn't necessarily translate to the generic plotweaver system. Which means we'd have to do a generic implementation, which would probably be a nightmare.

If a GM needs to have an actual scene representation of the cognitive realm they should just make a scene.

@TheFlyingPig
Copy link
Author

Regarding GM prep, every map will just have basically the same background for shadesmar. What I'm suggesting is reducing prep by showing soul lights where tokens stand and shadows of spren in the physical realm that are visible in shadesmar even when they are not in the physical realm.

@TheFlyingPig
Copy link
Author

The plotweaver system isn't defined enough yet to say whether this would be required or not. I accept that it's not likely to be required for it though

@TheFlyingPig
Copy link
Author

Another option would be to have a new "roof" type for shadesmar, then a practitioner could toggle their vision to see a part of that roof tile, and all tokens would affect it

@Dez384
Copy link

Dez384 commented Oct 30, 2024

The actual end goal of this request needs to be clarified, rather than just a proposed solution. As stanavdb previously stated, adding a “cognitive layer” isn’t feasible. While Foundry may have some additional capabilities over playing on a physical tabletop, anything asked of Foundry still needs an analogue to the ttRPG version of the game, and this is very vague.

So what is the specific end result that is desired? If someone needs to travel to the Cognitive realm, the token can be moved to a new scene manually or by an active tile effect (a tool within Foundry). Does a character just need to be able to see hidden or invisible things? A simple macro can be used to toggle a token’s vision between normal sight and “sense all” sight which gives an outline of invisible tokens.

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

No branches or pull requests

4 participants