Thank you for the feedback! There's definitely a tradeoff to work with when it comes to keeping things technical and finding a broader audience. I suppose ther

Thank you for the feedback! There's definitely a tradeoff to work with when it comes to keeping things technical and finding a broader audience. I suppose there's also room for a "simple" mode vs. "expert" mode interface or something along those lines to try to cater to everyone, while keeping the underlying mechanics of the simulation the same. Nevertheless, I acknowledge there's still room for improvement here for all audiences. :) As for the maps (and at the risk of sounding a bit paranoid here), I put them on a separate page to keep the embedded map pages from possibly getting access to the users' boat keys (since they're GET parameters and therefore part of the URL). I fully realise that putting "secrets" in GET parameters is bad practice, but in this case the bookmark-friendliness of having your own boat page URL seemed to be worth the tradeoff of putting something semi-secret like a randomly-generated boat ID/key in the URL itself. On the other hand, I didn't find it worth the tradeoff of potentially leaking everyone's boat keys to third party sites (however trustworthy they may be) through embedded components by putting the maps on the same page.