Terminal v1.3.0


major code changes 6 files changed, 508 line insertions(+), 130 line deletions(-) from my testing all features (excluding macro args) working Foundry V10-V11 verified

🖼️ Borders

you can see an imgur gallery of examples here

These are built using the included 14 images. But you’re not limited to these, you can upload your own images to use as borders.

⚙️ Macros

I am adding a different way to run macros. A new way which will allow for running the macro with arguments! Which greatly opens up what Terminal tiles can be used for. I did find out that macro arguments are not possible in Foundry v10 because there were only added recently in 11.295. So, this feature is unfortunately locked behind that release and above.

😁 UX Improvement

major User Experience improvement for selecting door IDs and linking a macro to a terminal. You no longer need to figure out how to gather the IDs for any Door or Macro and can simply select them from your view in a simple way.

Here are a couple other improvements to how you interact with forms:

  • hints as to what each setting does is hidden behind a hover on a information icon. This cleans up the look
  • several changes to make it follow a clean grid like look
  • settings collapse when Terminal is disabled. This brings focus to the required settings. As well as keeping things more accessible
  • placed a header over which settings are optional
  • improve style editor, now has section names. There is a link to my favorite online audio editor since I don’t have a way to balance audio for individual audio files.

📽️ Video + Image support

I was previously (unknowingly) only allowing for text type pages. This means when you create a journal page, and selected video or image these pages were broken in Terminal. Now they can be viewed easily. I even read some properties which can be set using the Foundry UI video volume, video controls, video volume, video autoplay, image caption.

🚨 Deprecation

You can join in on the discussion about this here

I am deprecating the entry and exit macros and fully removing them in release version 2.0.0 (which won’t come for a couple updates + months from now). This is because I am not entirely convinced that they would be better than my new macro method introduced this version. I was never happy with the exit macro and how it could be ran even if a player had closed the Terminal UI. I don’t see a way to make that work in a clear consistent manner. Having a button which the player clicks on in the Terminal UI is much more clear about what’s happening. If you disagree with this change you are more than welcome to make a case on the issue page. It’s still possible to get the exact same behavior with monk’s active tiles module.

known issues

  • I am aware of an issue where if the terminal is not enabled but a macro or a unlock door setting is changed it will collapse and disable the terminal. This is annoying and I will fix this in a 1.3.1 release. The code change isn’t as simple as I would hope and I already have a lot (hundreds) included in this version, so I’m pushing it down further down.
  • I realized it’s not clear who runs macros and what permissions should be set. I will update the text hints for that in the next update as well
    • for now you can know that entry and exit macros run by whichever user walks on or exits. While the new Run Macro setting always runs on the GM side to unlock all APIs.

🐛 Bugs squashed

  • tile config validation error notifications would happen on non-GM users
  • I was not handling other journal page types, it would just say “undefined” but still show as a button
  • Pressing Enter on tile config would interupt the standard event, opening the “Assign Journal” window instead of saving the tile config
  • replaced deprecated way of getting macro, this created large warning texts in the console
  • was selecting elements too generically, this would have caused issues if multiple tile configs were open at once.

Get Foundry Terminal

Buy Now$4.99 USD or more

Leave a comment

Log in with itch.io to leave a comment.