Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Is there a way to easily pass the id of the user who activates a macro in the terminal?

I creating a tunnelling thing where the players can try and hack each others networks and connect to other terminals but skip over their target's terminal.

(2 edits)

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.

Thanks for the reply. That would work but the macro I'm running needs arguments, mainly the target the macro pulls the shhs from. So I need a way to pass the user who is controlling the terminal to the macro which runs the gm side and emits the terminal for the user.

I know Monk's Active Tile Triggers has a way to do this but I already have a Run Triggers Button active and I don't want them to run at the same time.

(1 edit)

Gotcha. I think it’s about time I add a checkbox to allow my core macro feature to be optionally ran user/client side.

You can track progress here. Probably going to be a month before I get this change out.

An option to allow a macro to be ran by triggering player is in latest version.

However, I’m bundling it with some other things which I’m only planning on supporting Foundry v13+ with. So, it might be awhile but the feature will be waiting for you for when you upgrade to v13