> > > Hi Captains! The team continues to investigate an issue where some players may be stuck on a loading screen. We appreciate your continued patience! < < <
Jolan tru Captain!
Welcome to Legacy of Romulus!
If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game. (Please see the yellow text in the linked thread for instructions on creating a Reman.) (Not seeing your pack in-game? Please see the lime-green text in the linked thread above for information.)
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
Thanks SO MUCH for all your support, and we'll see you in-game!
- The Star Trek Online Team
"Login failed for unknown reason" error
Missing additional character slot for current/ lapsed Gold Members
Slow patching in the launcher
A bug that involved Romulan Liberated Borg captains and their skills once they chose an ally
Alright guys, as many of your know there's a lot of maps in the Foundry that are basically useless because they're so tiered, you really can't place objects in certain places on a horizontal map and be sure you're getting it where it needs to go vertically.
When the Foundry first launched, the way around this was to use the /LOC command line to get the exact placement of where you were standing so you could put your objects in the right place.
Well then someone decided to change all the Foundry measurements to something else, making /LOC entirely useless unless converted with math. What I'm trying to figure out is, what do I need to divide by to get the appropriate number here?
And Foundry devs, why can't we get this functionality built into the Foundry itself so we don't HAVE to do this? Without it, there are SEVERAL maps that are damn near impossible to build on.
I am a Cheestah.
Check out my Foundry missions
Fed: "To Helna and Back", "Rema Donna", "Animations with Helna", "Mudd's Weapons", "Waiting for Wednesday"
KDF: "Time the Enemy", "Time the Ally", "Time the Traitor"
provisionally it seems to be (<loc number> / 3.281) = real number. Now if this isnt 100% precise I welcome a refining of it, additionally I welcome this being implemented in the back end so that math isnt required everytime you want to use it