> > > Hi Captains. Thank you for your patience! We've got our top Engineers checking in on the errors you are reporting. More updates as they become available, so watch this announcement section. < < <
UPDATE! We will be bringing down STO in 1hr 22min for emergency maintenance. ETA is 2 hrs (2AM) PDT. Details here: http://sto-forum.perfectworld.com/showthread.php?p=10193141#post10193141
Update! The queue is clear for now :) Thanks for your patience as we worked to get all players in. (Note: There may be small, sporadic queues as more players log in.)
Update! We are aware that some players are seeing an error upon login and are working to resolve this.
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.)
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
Okay, I tried to send in a bug ticket on this but the profanity filter kept kicking it out. Can find the profanity?
That said, I am an avid binder; have bound many of my available powers in one way or another to various keys. I believe I have found a flaw in the binding system. The semi-colon ( and the comma (,) do not accept binds properly. The comma will not accept any command and the semi-colon will only accept a partial command (the first in a multi-string command).
Specifically the below are the commands that i have attempted to bind both manually wiht the "/bind" command and through manipulating the bind file itself.
This one is associated with N, M, period (.). fwd slash (/) to issue commands in a similar fashion.
It seems that when binding these keys there is a difficulty with the process in that does not recognize the syntax (bind <string> <string>) for these two keys and renders an error message: "bind" takes 2 argument(s). Additionally, the unbind command is similarly nonfunctional for these keys as well and renders an error message: "unbind" takes 1 argument(s).
If someone else who binds regularly could test this discover on their system I would greatly appreciate it; that way we can definitely rule out a give computer at fault.
Since I am unable to get this to Support through the bug ticket process. Cryptic, could someone please look into this problem? I know you are all busy with fixes that have a much, MUCH higher priority, but I hope that this could be a quick fix which you could just slipped in without much ado.