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

Using "inMemoryOnly": true in a GrantItem that grants a condition which also make use of inMemoryOnly will silently breaks the character sheet #18250

Closed
reonZ opened this issue Feb 9, 2025 · 3 comments · Fixed by #18293

Comments

@reonZ
Copy link
Contributor

reonZ commented Feb 9, 2025

I dunno to what extent this breaks a character or if it is just the sheet, but adding this RE on an effect will prevent the character sheet from being closed if it is opened while the effect is on the character.

The effect grants the condition Paralyzed, i have narrowed it down to "inMemoryOnly": true being the culprit and it happens for other conditions (e.g. Restrained) that also grant themselves other conditions using inMemoryOnly.

There is no error in the console and once the sheet is opened, it cannot be closed even if you remove the effect after the fact. Also, this issue doesn't happen to NPC sheets.

{
  "key": "GrantItem",
  "uuid": "Compendium.pf2e.conditionitems.Item.6uEgoh53GbXuHpTF",
  "onDeleteActions": {
    "grantee": "restrict"
  },
  "inMemoryOnly": true
}
@CarlosFdez
Copy link
Collaborator

This is definitely a weird one to figure out, but it seems something is going wrong in the submit pipeline. Same issue occurs if you try to make any changes like adding hero points.

@stwlam stwlam added the nonrepro Issues that have not been reproduced label Feb 16, 2025
@stwlam
Copy link
Collaborator

stwlam commented Feb 16, 2025

Not able to reproduce; check modules.

@stwlam stwlam closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2025
@reonZ
Copy link
Contributor Author

reonZ commented Feb 16, 2025

Not able to reproduce; check modules.

There was no module involved and i doubt supe said that without also testing.

chrome_JeX4BgLcsj.mp4

Don't just dismiss it like that without at least waiting for an answer.

@stwlam stwlam reopened this Feb 16, 2025
@stwlam stwlam removed the nonrepro Issues that have not been reproduced label Feb 16, 2025
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

Successfully merging a pull request may close this issue.

3 participants