Is there a Macro or API to help w/ adding monsters from compendiums?

Backstory: I *constantly* have problems with the drag and drop of monsters from the compendium onto the map. It will do it on a delay or not do it at all. It will create a weird glitch sometimes where an unusable link gets dropped into the top left corner of the screen. I'm always having to refresh. It's a pain. So really my question is, is there a macro or API someplace that allows for just...right click on a monster and "add to map" or something similar? Thanks!

I'm afraid there isn't.

Well, damn. Thanks anyway. Dragging monsters onto the map is my least favorite task for the amount of times it glitches for me. 

That does sound like a terrible problem.  I haven't done that much recently, but I can recall it being an issue in the past at times.  Doing the work during non-peak hours might be less frustrating.  Filing a bug report and collecting the Javascript Console Output and some other things might let Roll20 fix it.

Just double-checking: you're only doing this for new monsters which don't yet exist at all in your game? You can copy & paste tokens on the canvas to exponentially increase goblin reproduction speed, once they exist in the game, rather than dragging them on one at a time.

I have the same issue Amber, it really does  suck. Especially for ad hoc summons, had a shaman summon an allosaurus in my last session (12pm GMT, definitely not prime time server load-wise), drag>dropped from the compendium, no duplication, it took 25 minutes to finally show up on my screen. The players could see it straight away however :( Never thought to grab a console log and can't offer any advice on how to fix but... at least you're not alone... yayyy...

Amber and Ziechael, does the monster appear in the Journal? I ask, because I've noticed monsters don't drop on the map like they used to, but when I look in my Journal, they are there, usually at the very top...

Yup, I get the journal entry straight away but no token on the map (that I can see, although everyone else can). Subsequent attempts to add from the journal tab just add more and more tokens that I can't see (although everyone else can lol) until they ALL appear 15-20 mins later... I still remember the first time, the players freaked out about 7 monsters suddenly appearing on the map when it was me just trying to add one that I could see :D

Lol!  Definitely should look for errors in the Console Log and the Network tab.  It would also be interesting to know if the API gets an add:graphic  and add:handout  for them immediately.  I'll investigate that angle.  

The Aaron said: Lol!&nbsp; Definitely should look for errors in the Console Log and the Network tab.&nbsp; It would also be interesting to know if the API gets an add:graphic &nbsp;and add:handout &nbsp;for them immediately.&nbsp; I'll investigate that angle.&nbsp;&nbsp; I have been modifying and adding to your API Heartbeat script (current version can be found on <a href="https://gist.github.com/MartijnSanders/6d47f5d47ad5c379532368349856ac7d" rel="nofollow">https://gist.github.com/MartijnSanders/6d47f5d47ad5c379532368349856ac7d</a> &nbsp;). Next to changing the player color, this script now also: - every thirty seconds logs a timestamped message to the API Output console.&nbsp; - logs a lot of timestamped&nbsp;events to the API Output console.&nbsp; - logs timestamped&nbsp;field changes for some change events Based on running this the API Output Console in a seperate browser instance (and saving the html page), till now my interpretation of the logs is that the API script servers do not have a (significant) delay.&nbsp;

Interesting.&nbsp; I've also been working on it and will likely release a new version this week.

Martijn S. said: Based on running this the API Output Console in a seperate browser instance (and saving the html page), till now my interpretation of the logs is that the API script servers do not have a (significant) delay.&nbsp; I've gotten the same results, which I actually mentioned to the devs last night.&nbsp; While the API can experience latency from execution issues, I think most of the current "API Slowness" has more to do with communication between the API Server and the Game Shard, though I can't really know that for certain as I don't have access to the architecture there.&nbsp; I'm hoping that investigation there will yield good results.

My hunch is that it is a timing/congestion issue within google firebase and/or connectivity/congestion issues between the browsers of individual users and firebase and/or the cloudflare API route.&nbsp; ... thats sounds complex.

I think it's the API Sandbox &lt;-&gt; Firebase connection.&nbsp; During a slowdown where I was testing the above script, communication between clients and Firebase was snappy, but API commands were taking forever to come back.

Yes there is a way of randomly selecting tokens into the map, I saw it explained in taking20 on youtube. You will require use of roll tables to randomly select your preloaded tokens...

I believe that would be creating a rollable table token and choosing a random side on it. That's not quite what the OP is after, if I'm not mistaken.&nbsp;

Oosh said: Just double-checking: you're only doing this for new monsters which don't yet exist at all in your game? You can copy &amp; paste tokens on the canvas to exponentially increase goblin reproduction speed, once they exist in the game, rather than dragging them on one at a time. Yes, only for new monsters. And like Ziechael, the biggest issue is when I'm trying to do it ad hoc bc my players have suddenly decided to be murder hobos or they've summoned something or my druid turns into something I've never seen them turn into before. It can freeze up my entire game and force me to restart in the middle of it which ultimately is...whatever, it doesn't kill anything, but definitely dampens the mood.&nbsp; Re: journal, yes, it appears in my journal sometimes but not always. I will try to capture it the next time it happens.&nbsp;

i think there isn't.