Of course, go ahead. Feel free to DM on discord if you’d like. It’s “codabool”
A member registered Aug 10, 2023 · View creator page →
Creator of
Sci-Fi maps ready to go. Build stories not maps
A customizable interactive terminal from which players can read and reveal journal entries
Recent community posts
I think the issue you might be getting is because Terminal uses a GM proxy for macros. If I’m understanding right, I think you would be able to do what you want if the macro was simply ran on the user’s machine.
If that’s the case, there is currently one way to run macros from Terminal without a GM proxy. This requires Foundry V12+ as it uses Regions.
- Create a Region, make sure its in a location no users can access, so as to avoid this going off when you don’t want it.
- setup the region as shown in the picture (left & top right windows)
- Then open the “Trigger Regions” button on Terminal. Link your Region to the Terminal (bottom right). Simulate the same event found in the behavior you created.
- Make sure the chosen macro is given observer for everyone.
- You’re done, a new button will show in Terminal which can run macros on the User’s side.
from there you can get the user’s id with game.user.id
Again, not totally sure if I’m on the mark here. So, let me know more details if this isn’t what you had in mind.
You could do this in one of two ways.
The simplest is to chain the Terminals together. So, each Terminal can Secure Shell to the next one.
The more complicated way requires some scripting but I’ll walk you through it. This way also requires using Foundry V12+, since it uses Regions. This will create a one-to-many relationship of Terminals. You’ll need to create a new Region. Keep the Region in an area players can’t get to, it will only be used for scripting. Then create a “Run Script” Behavior. For an example see the screenshot below. I created 2 Run Script Behaviors and renamed them to “Open Terminal 1” and “Open Terminal 2”. I have the code later which you’ll want to enter for each Behavior.
You’ll want to have each of your behaviors use a separate “Subscribed Event”. For mine I used “Token Enters” & “Token Exits”.
Now we need to link these Event Behaviors to the parent Terminal. Open the tile config for your main Terminal tile. Then open the Trigger Regions window (see screenshot below of the opened window). Add the new Region. You’ll want to add it multiple times (since I’m only linking two Terminals, I’ll add that same Region twice).
Then to finish the link, we need to edit the “Simulated Event” field to match, one to one, with those Behaviors we created. So, for me that’s the “Token Enters” & “Token Exits” events.
I know this gets a pretty complicated and likely confusing. Try and match what I have in the screenshots as best you can to just get it working.
What this does is every Region that’s added here will become a button in the main Terminal. The button will simulate your chosen Region event. This trigger all Behaviors that are subscribed to that event (in our case it’s one-to-one). Since the Behaviors are script Behaviors this runs the code you have in the Run Script field.
Now, that everything is linked let’s go back to your “Run Script” Behavior. You need to actually define the code to run. Copy this code into a notepad:
const TILE_UUID = "PUT_YOUR_TARGET_TILE_UUID_HERE"
const terminalOpen = Array.from(foundry.applications.instances.values()).find(a =>
TILE_UUID === a.context?.tuid
)
if (!terminalOpen) {
new Terminal(TILE_UUID).render(true)
}
Replace the TILE_UUID variable with any one of the target child Terminal’s UUID. Then enter your edited code into the Behavior’s Script field. That finishes one Behavior’s “Run Script” but we have multiple. For each child Terminal you want to link, update the TILE_UUID each time and paste your code into a different “Run Script” Behavior.
That should be it. There are only a few extra considerations. This bypasses validation on your Terminal settings. This bypasses the initial Item and Skill checks (password should still work).
Eventually I’m sure Foundry will support running Macros with arguments from Regions and this will be simpler but that isn’t happening anytime soon.
I haven’t been able to reproduce the duplicate tab issue like in your screenshot. But I do have quite a few updates I’ve put out. Latest is currently 1.3.5 now and has a more fully featured method for using macros to open a Terminal.
In order to use the macro you can follow these steps:
- Upgrade to latest
- Open your compendium and you should see a new entry for “Terminal Macros”
- open context menu (right click windows or two finger click on mac) on either an individual macro or on the compendium itself and import macros
- I recommend using “Monk’s Active Tile” module to supply either macro with arguments.
- You will need to pick if you want to open the Terminal for all users, or for a specific user. They both are their own macro. So, in Monk’s Active Tile menu select the appropriate one.
- Fully configure a Terminal tile in the scene. (There is a requirement that all users and GM are viewing the scene which this will happen in)
- Take the Tile ID and supply it as the first argument.
- (optional if using a macro for a single user) as a second argument (Monk’s Active Tiles expects arguments to be separated by spaces) provide a User’s ID
- Activate the tile, which runs the macro
I’m going to edit my previous comment that contained an example macro since one is now included in the module.
Are you on the latest version 1.3.3? Yeah this is a potential issue with trying to open the Terminal with a macro. It is bypassing some of the validation I’ve written in.
You will need to assign assign a style to the Terminal from the tile’s config before trying to open it from a macro.
I do need to fix the visibility of the close icon. I can do a quick fix for that in this week but for now there is a hidden close button that is still clickable where this image points to:
