Jump to content
Dante Unbound: Share Bug Reports and Feedback Here! ×
  • 0

_1


Husla
 Share

Question

9 answers to this question

Recommended Posts

The _1 is caused by you disconnecting suddenly and reconnecting to the IRC server that allows communications. The server sees that a "person" with your name is still "active" on the server, which forces it to append "_1" to your name in order to make a unique username. The "person" that already has your name is a ghost; it is your old connection before you got disconnected for whatever reason. It won't do anything at all, and the IRC server wants to wait a certain amount of time before forcibly kicking it.

In Warframe, this is a problem, as there is already a unique identifier which is used, in the form of your username on the Login screen. For some unknown reason DE insists on not fixing this issue.

The resolution for this is a 5 minute job as the IRC administrator (And I really hope they do it soon), and that is, in the case of a name conflict occurring, to boot the "player" that occupies that name on the IRC server. As it is your old connection, this will forcibly free up the space at the point in time the IRC wants to use it. In the case of Warframe, this is perfect for what is required.

In the meantime, this ghost username needs to time out in order for your name to be freed up. This can usually take between 2-5 minutes.

Edited by Azure_Kyte
Link to comment
Share on other sites

The _1 is caused by you disconnecting suddenly and reconnecting to the IRC server that allows communications. The server sees that a "person" with your name is still "active" on the server, which forces it to append "_1" to your name in order to make a unique username. The "person" that already has your name is a ghost; it is your old connection before you got disconnected for whatever reason. It won't do anything at all, and the IRC server wants to wait a certain amount of time before forcibly kicking it.

In Warframe, this is a problem, as there is already a unique identifier which is used, in the form of your username on the Login screen. For some unknown reason DE insists on not fixing this issue.

The resolution for this is a 5 minute job as the IRC administrator (And I really hope they do it soon), and that is, in the case of a name conflict occurring, to boot the "player" that occupies that name on the IRC server. As it is your old connection, this will forcibly free up the space at the point in time the IRC wants to use it. In the case of Warframe, this is perfect for what is required.

In the meantime, this ghost username needs to time out in order for your name to be freed up. This can usually take between 2-5 minutes.

 

^This. nothing much you can do about it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...