Roll20 Feature Area | Suggestions Thread for this idea? | SUGGESTION IS: |
Copy Game (API Scripts) | This current thread. | 1. Add ability to Copy API Scripts in Copy Game feature. |
Transmogrify (API Scripts) | Also this current thread. | 2. Add ability to Copy API Scripts in Transmogrifier. |
Transmogrify (Macros) | This would make a good new, separate thread. | 3. Add ability to copy Global Macros in Transmogrifier. |
Copy from this Game...... Players and Player Settings (Including Macros) Pages Decks Chat Log Journal (Characters & Handouts) Jukebox Playlist Game Forums
RMcD said:
I meant the copy campaign feature, my bad that that's not clear.
+1 just realized that copy game DIDN'T do this... so much time lost to try and redo all the scripts...thanks for the comment telling me you can't just copy from the api panel, so now i need to go back to the raw.. annoying.
Wow, I thought this was done in part of the game, but, yeah, API Settings aren't copied over with Copy Game/Transmogrifier.
At least to have it as a checkbox whether you want to copy it or not, just like being able to choose to copy players or chat, etc.
Even if it doesn't copy state (and I wouldn't want it to be the default, certainly), I am all in favor of this idea. On the surface, it just seems like you are copying text files. I'd love to hear from someone more knowledgeable as to what hurdles need to be overcome to make this happen.
I recently upgraded to Pro for API scripts, and I had no idea that backups (copies) of my campaign don't include the API scripts. Seeing that this thread was started four years ago (!) makes me sad. Can someone on the dev team (or someone who knows) please explain why this hasn't made the cut? It's really more a bug (API scripts fail to copy during Copy Game process) than a feature request. Thanks.
Well, one thing that they may or not be looking at is that anything dealing with character sheets and the api is restricted to pro, so a lower pool of voters. They tend to only look at things with 200+ votes unless it ties into something they are already working on. Look at the number of votes for this suggestion and you see how that works out. Hopefully they will set a lower voter threshold for things like this eventually.
From another prospective pro's are the ones financing Roll20 and anything that improves Pro would presumably make more people sign up, or keep renewing.
Seems like this suggestion and a few others boil down to: When a feature says "copy" it should create a copy. There are a few features that make duplicates/copies of one thing or another, and many of them fail to do what the user anticipates, resulting in extra work, and sometimes frustrating situations where something appears to be broken, but is actually just missing.
I think there needs to be an evaluation of various "copy" features throughout the system, and they all need to be corrected to function as expected.
Since scripts are set up on a per campaign basis, not copying them when you copy the campaign is a bug.
This (emphasis added).
Josh O. said:
Seems like this suggestion and a few others boil down to: When a feature says "copy" it should create a copy. There are a few features that make duplicates/copies of one thing or another, and many of them fail to do what the user anticipates, resulting in extra work, and sometimes frustrating situations where something appears to be broken, but is actually just missing.
I think there needs to be an evaluation of various "copy" features throughout the system, and they all need to be corrected to function as expected.
Since scripts are set up on a per campaign basis, not copying them when you copy the campaign is a bug.
I have also just hit this: having started setting up a game, and adding all the scripts etc., I thought it would be very useful to copy it to use as a 'blank' game. Unfortunately, since 'copy game' does not, in fact, copy the game, I would still have to set up all the API scripts etc...
Just copying the scripts (which should be easy!) would be sufficient even without the state, but really it should be a complete copy and anything else is either a bug or should be displayed in big flashing red letters 'this feature doesn't do what you expect' (although if this robust approach to UI was taken throughout Roll20, the endless flashing would get quite annoying...).