I am seeing and can't get rid of someone else's macros? Help!

I dm a game of Pathfinder 2e. For some reason there are another players macros in my "collectionc". I cannot edit or delete them, I click and nothing happens. I can however roll them and they always roll for this one player who probably made them. If I click a character token they always show up on the top left hand side corner. I can add new macros and delete them. But his macros are stuck in my collections and appear whenever I click any token. How do I get rid of them or solve this?

Are you the creator of the game or a co-GM?

I am not the creator but the only DM. I mean I had a friend create it for me for dynamic lighting. But I can tell him to do what needs doing. And the macros I see are of a different player, not the creator. I don't know enough about macros.

Ziechael hit the nail on the head. They are creator GM macros. A non-creator GM cannot delete or edit them. Ask the creator to remove them if they're not needed. If a player is actually using them, they will need to be copied into a character sheet as Ability macros (either that player's sheet or a Macro mule) before they're deleted.

Ok, so it sounds like someone else is creating macros and marking them as visible to 'all players' and possibly even checking the 'token action' box as well. This will mean that everyone can see them in the collections tab, and run them from the chat, and that all tokens will have those macros attached to them. The likely solution is to ask the players to see who is doing it and tell them that they are likely best off doing them as abilities on their sheet instead, that way they can tie them to their token only and not pollute the collections (I call them global) macro area which should be for 100% universal stuff only. The creator of the macros will need to be the one to edit/delete the problematic macros though... I'm not aware of any way around that but my players never try to be helpful so never had it happen to me sorry. [edit... shoulda refreshed lol]

Thanks a lot for that. I did talk to him and they used github extension with a browser and accidentally added DM macros so they were polluting me. They took care of it so no more issues. We have some other DMs in our group that kind of don't approve of that and start pointing towards possible cheating. In this case I could see the macro commands as rolled and combined with obvious logic there was nothing sketchy going on. But, I am more trusting than others. Either ways problem got solved because I talked to them and they removed those. I am new and barely making sense of templates. So, I found it very odd.  Thank you Zeichael and everyone else.

Out of curiosity would this still have happened if I was creator and DM?

As soon as you start dealing with third party browser extensions all bets are off so I couldn't say. Co-GM's have slightly less power in a game than the original creator who is all powerful. Players have very little power to influence global things like that but as a permanent GM I'd have to do some testing to be sure lol.

OK, did some testing and players shouldn't be able to create macros that make the GMs life a misery. They don't have the option to make them visible to others so should only show on their list (alongside any others that the GM has marked for them to see). They CAN set them to be token actions BUT that only applies to their view and tokens that they can control as one would expect. Short answer, only Creators and co-GMs can make a mess :)

However, a Creator can make a macro that a promoted GM cannot edit. I found that out the hard way.

In this case it was not the creator or co dm (aka me), well I am the only DM, the creator does not DM. But, the players used a github extension and somehow imported DM macors that were visible to both creator and CO DM. They did get rid of it when asked, so it is not a problem and their algorithm and calculations are completely visible. I have the templates they used too and all simple and normal. But yeah apparently this problem arised due to extensions importing DM macros which somehow a non DM player could do. Maybe a roll20 bug? Anyhow they solved it. Even they did not know this could happen. Either ways thanks and this does happen it seems.

Roll20 can't and won't support third party extensions and any aberrant behaviour that may arise due to things like that... they might be interested to learn of something that allows players to abuse GM only functionality though. Might be a 'good citizen' thing to drop them an email at <a href="mailto:team@roll20.net" rel="nofollow">team@roll20.net</a> with some details so they can deal with, be aware of or otherwise ignore it at their discretion :) Glad you got your issue sorted though!

To be fair I am a total noob at macros but roll algorithms are things I do understand and how fudging rolls is just hard. The whole "cheater" did not sit well with me. I mean accusing one of my players. Saying stuff like how have they not rolled a nat 1? Well it was the first session and just 1 combat. But anyways issue sorted. I will drop an email.

An extension that allows a player to abuse GM-only priveleges doesn't sound like something you want in your game. Whether or not the player has ill intent, the extension sounds like it has the capability to mess up the campaign. What functionality is the player actually using it for? Never mind, figured it out. It's the macro importer/exporter attached to VTTES. I just had a play with it, it exports a .json of all selected macros and has a "visibleto": "-M-EUV4cgUr-9n1XykzX" field for each macro. If this is set to "all" and imported by a player, the macros show up in the GM list (and everyone else's, presumably) and cannot be edited. This isn't ideal behaviour. I don't use Github myself, not sure if anyone feels like doing the deed of reporting the issue to the creator (unless they lurk about here under a different name?). I'm assuming this isn't intended behaviour, the extension seems to have plenty of other GM-only features, so presumably a GM check on a macro import isn't terribly difficult. Obviously this isn't Roll20's problem, but that doesn't mean it won't pop up again in these forums... after all, the person affected isn't even using the extension.

They imported macros. And since macro algorithms are fully visible they all look clean. It makes nesting easy.

Yes it was VTTES. It is kind of solved now since they removed the macros. ANd again the initial jumpy nonsense which pointed towards cheating still seems impossible. Just extra tech and the player was quite prompt in helping me clear things that were polluting my collection so no harm done.&nbsp;

Oosh said: Never mind, figured it out. It's the macro importer/exporter attached to VTTES. I just had a play with it, it exports a .json of all selected macros and has a "visibleto": "-M-EUV4cgUr-9n1XykzX" field for each macro. If this is set to "all" and imported by a player, the macros show up in the GM list (and everyone else's, presumably) and cannot be edited. Does that happen when imported by a player who isnt a GM? I'm wondering how that would be done, if possible.

Yeah, I used a dummy account with no GM powers. No idea how it's done, sorry!&nbsp; Presumably there's nothing stopping a player from editing the "visible to" field, it just isn't present in the UI which generally means they can't change it.

Well I did inform the roll20 team. Maybe you all should too, give them extra motivation.

Roll20 has no control over VTTES.

But they could tighten up the permissions on Roll20 so browser extensions can't do this.

Rabulias said: But they could tighten up the permissions on Roll20 so browser extensions can't do this. I dont think they can. I dont know exactly who the extension works, but it's probably just sending API chat commands, and there's no way to tighten that up without restricting the API for all users. If its using pure javascript solutions, there's even less roll20 can do about that.

From my understanding, there is little to nothing Roll20 can do about something like VTTES.

I used an API a few years ago to find and delete macros. Maybe this will still work. Here's the thread .

Rabulias said: But they could tighten up the permissions on Roll20 so browser extensions can't do this. I have realized that what I said here might be taken different ways. I was not talking about Roll20 preventing browser extensions like the VTTES from working. I was talking about the specific issue that Oosh tracked down: that a player can make macros appear for any other player in the game, even the GM, and the players and the GM cannot remove them. I believe Roll20 intended that only GMs would have the power to make macros display to players in their games. This issue has shown that it is possible to circumvent this. There needs to be more than just the "visible to" setting on macros to determine what shows up on players' screens. Roll20 needs to check if the player is a GM before automatically adding the macro, or even better, allow players to see the macros shared with/visible to them, but allow players to choose which ones to show on their own quick macro bar. I believe this is totally doable by Roll20, and is what my rather vague statement was referring to.