I’m in the process of migrating to free and open source.
EDIT: migration finished, the module is now free and open source. Still under the same package id terminal
Thanks for the detailed feedback. It’s my first module and I’d like to make a few more. So, this is really helpful.
Thanks for the heads up, I’ll remove the PSG rules from the app until I get approval. Yeah the app is human made too. I do web dev in my free time. I can add a human made label on there too.
You’ve hit the other high priority task I have lol.
When I released the module campaign codex hadn’t come out with their new update. I need to rewrite my integration with them now. I’m not surprised that it is incompatible with it at the moment.
Oh yeah weird, one of my imports is broken. I’ll fix that right now but the CC integration will take a couple days.
EDIT: fix is out with version 0.0.5
Ok, understood. There currently isn’t support for that kind of nesting. The two workarounds which come to mind are
any html can go in here
relevant html code
<details>
<summary>click to open</summary>
<p>any html can go in here</p>
</details>
There is a visual for when the state of a door changes.
Assuming you are talking about journal permissions. There is not currently support for stopping permission changes for that. As well as support for reverting.
I have looked into a permission revert feature but ultimately did not like the solution I came up with. I might revisit it at a later time.
You might have to explain more of what you mean for your second question. There is support for adding multiple doors to unlock. You can also rename the button to “Airlock One” for example.
Do you mean the player would have to unlock door 1 before they could do door 2? If you want more control over the door actions. I’d recommend looking at adding “Locking or Unlocking Doors” as a skill check (found in Auth tab under Terminal tile config). That way you’ll get a dialog and can control when those actions are allowed.
Let me know if that helps.