Gauss said: Ken S. said: It would appear that despite being characterized as "system agnostic", this is a jumpgate feature that does not work in Legacy games. Certainly it failed for me in my Legacy testing game with "unknown command" or something similar, while working in my current (jumpgate) game. System agnostic means game system, ie D&D, Pathfinder, WoD, etc. Not which VTT engine is being used. Roll20 has stated that the Legacy VTT engine is not being updated anymore, new features will be on the Jumpgate VTT engine. It would still be clearer to simply say that. The new system is only a couple of years old at this point. My games are all jumpgate, but some DMs I play with are still on legacy (despite quite a bit of lobbying on my part) and legacy games are still "supported" to the extent that they exist and are functional. I'm not suggesting that the new features need to work with them. But there are users of roll20 who haven't converted, and that community needs to be considered. If only because pointing out that there ARE things they're missing might serve as an incentive to move. I do want to note that I appreciate the new feature, and I certainly plan to use it in my games.