Definitely can try and get that fixed for you. I unfortunately was not able to replicate that on my end. I tested in V12.

I’m guessing our setup is different.

Go ahead and use “Report a Bug” button. It’s fine to leave the content blank. This will email me more information for your system (e.g. Foundry version, modules, browser).

That sounds cool. I do think there is another module (it’s free) which does something like what you’re describing. Have you seen console? Let me know if that works for you.

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.

1. 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.
2. setup the region as shown in the picture (left & top right windows)
3. 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.
4. Make sure the chosen macro is given observer for everyone.
5. 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.

Looking into this!

EDIT: should be fixed now in v3.1.7 thanks for the report

I have added a splash media setting that you can find on the style form. It has two “modes”.

1. If you upload a video it will replace the loading bar and ASCII entirely

2. If you upload an image it will use that as a background while keeping the standard ASCII and loading bar

I still need to add more layouts, text animation, and default styles but it’s getting there.

EDIT (4 months later update): this behavior is NO LONGER TRUE as of 3.1.6+ (October 2024). Showing the ASCII art + Loading bar is now its own configurable setting in the style editor. Regardless of the file type used for the splash.

That’s a cool implementation. I haven’t actually tried placing them on top of each other like that.

For updating the flags you’ll actually want to use Foundry’s setFlag() function. This is present on the document object of the tile.

Here is an example:

canvas.tiles.get("id of tile").document.setFlag("terminal", "enabled", false)

Let me know if that works better.

I am eventually adding a feature to open other Terminals. It’s good to hear there will be some demand for that.

EDIT: this feature has been added by the name “Secure Shell”. There is also included compendium macros that can be used for opening a Terminal.

Yes, when configuring the Terminal inside the Tile config. There will be a checkbox to add a button for any user that views the Terminal UI. This button when clicked will explore all the Fog of War for the current scene for all connected players.

Let me know if you have another other questions 🙂

As a warning if you like to stay on the latest Foundry version I have yet to find a way to make this feature work on the unreleased version 12 (Which won’t come out for another couple months). I reached out the Foundry devs but it doesn’t seem like they are going to help me find a solution to it. There are APIs I can hook into but they get complicated very fast.

So, just something to be aware of. This feature may only be here for a year if you stay on latest Foundry.

Yes it is 🌞 I do it all the time and would recommend.