Things I wish I knew before I wasted a ton of time on pro features: -The real money is in the transmogrifier feature, you can use it in so many awesome ways. Store all your bestiary in another session, drag and drop over monsters on demand keeping your live session crisp and clean of garbage. Same goes for adventure modules, install them in one session, then drag and drop over what you need for the nights live session. -API's are great but there are pitfalls involved with the whole process. First off, theres a shit ton of scripts out there that are amazing but just add massive amount of time to prep and sometimes even drag out live gameplay for nothing other than showmanship and in some cases they even still look awful. I wasted so much time on learning this the hard way. There are a *ton* of scripts that are seemingly popular here on the forum amongst the warriors that are absolutely awful to run as a DM in a session as they either add massive prep time, add time drain in live sessions, or they lag the hell out of your players and yours machines. I can't tell you the ones I feel do this because it would devolve into forum warriors arguing over their own experiences talking past themselves. I'll gladly respond to you in a DM letting you know what ones I found were efficient though. -There is a crash in the sandbox that does not report any change whatsoever in the sandbox, its been around for a few months now and a new user is going to be completely confused when it happens. IMO I feel like this crash is caused when another sandbox crashes that is hooked to a session you own but aren't currently running(so don't share sessions with strangers). The only way you know this crash has happened is your random api related macros in session will suddenly do literally nothing. Simply fire a manual restart of the sandbox, which is why you should always have a tab open to the sandbox page to hit the restart button. The more common crashes are nothing to panick about, just restart the sandbox if it occurs, beware of poorly written manual scripts out there as they will crash often and add to the above opinion on why api scripts are sometimes just not worth running. There are highly popular scripts here in the forums that crash way too often for my taste. -Dynamic lighting. Oh boy, beware of the UDL defenders but UDL does not properly work and even if you do have a table where everyone can use it well, a simple adblocker lets a player disable UDL and see the whole map. Don't use it. Enable Legacy Lighting and your life will be so much better. I honestly do not believe the forums tell the true story of the current state of dynamic lighting on this service. I have NEVER had a table that could run UDL effectively and EVERY time I have enabled it, done tons of prep for it, it has ALWAYS burned me with multiple hours of lost playtime trying to make the stupid thing try to work. LDL always works.(period). Reliability is the greatest thing any feature can have and roll20 does not understand this concept. Imo UDL suffers the same problem as those complex api's I tried to warn you about except that UDL and LDL do the same thing and the stuff UDL does above and beyond...just don't matter. You are playing dnd not a video game. If they wanted us to test it properly they should have given us a simple effective way to toggle between the two types and made the API's that control both work regardless but they didn't, so we either have to have api's setup for one or the other...or both and spend half an hour going to each page and all player tokens resetting back to LDL when one players UDL screws up, the devs just have no idea how frustrating unreliable features are to their paying customers.