Who reset the nicks?

[XO-MANOWAR]

I just tried to log on to a different zone than i usually played(using another alias),and was prompted to register the nick.As this aroused my curiosity,I tried a couple of my other alias nicks...they too prompted me to re-register them.Anyone know what is going on and WHY this was done?Ive had these for quite sometime,seems a bit reckless to start deleting player-database entries imo.But I'll wait to see the logic behind the madness before I say more.

[Hakaku]

Not all zones are connected to the same user database server (aka biller), as such, your username, password, and other personal information aren't carried over. The prefix SSC in the zone name typically denotes zones that are connected to the central biller.

 

It should also be noted that if your username exceeds 18 characters and you play in a zone that uses the Subgame server, your name will get trimmed down to 18 characters in an ASSS zone, which will prompt a new registration form. Similarly, if your username in your Continuum profile exceeds 18 characters and you normally play in an ASSS zone, when you switch over to a Subgame zone, you'll be prompted a registration form since Subgame accepts up to 23 characters.

 

Player names don't get reset on the SSC biller unless they've been inactive over a certain period of time (depends on your usage).

[Samapico]

Names with low usage (say under 100 hours) can get reset after a few months of inactivity. The process is completely automated too.

[PoLiX]

Ignore them, usage isn't the key factor

 

There is one zone listed as SSCI which isn't on SSC (though got approved now, just waiting on IP to be added to firewall). But if you had a prompt before entering that the zone wasn't connected to the central network this would be the 1st clue.

 

Though you will notice hundreds of names reseting over the next year or 2, as most names actively used for a few years after the pop booms are hitting the point where their data meets the reset standards.

 

Amongst the occasional hiccups where the reseter program goes nuts, kills a few extra names, and then crashes the biller for a couple days. But that has only happened once in the past year or so.

[XO-MANOWAR]

All very interesting gentlemen,but I logged out of the aforementioned zone and back into DSB after the first fail.All following attempts were made in DSB zone where "most" of the nicks were created.Its not that this is a epic problem,its just the first time it has happened to me in 12 or more years of playin Subspace.Polix is there really a time tag on nicks for playing or not playing?

[PoLiX]

It is based on a few things I can't really disclose...

 

1. Because Priit has never technically documented the entire program.

2. Even if we knew it 100% through, name whores would abuse the info.

 

But what we do know from Priit, and other situations, there is 3 key factors.

[»Maverick]

But what we do know from Priit, and other situations, there is 3 key factors.

 

 

Hmm let me guess;

• Having a squad tag
  
• Having a banner
  
• ?? (I would say usage but you just said that isn't a key factor)
  

[Hakaku]

I assume the last login date/time plays a role. And I'd also be surprised if the biller deleted players who have powers on the biller.

[PoLiX]

But what we do know from Priit, and other situations, there is 3 key factors.

 

 

Hmm let me guess;

• Having a squad tag
  
• Having a banner
  
• ?? (I would say usage but you just said that isn't a key factor)
  

 

Nope, Nope, and I said it isn't a key factor, but it is a factor.

 

And of course last login plays a role.

 

The biller stores a lot more information than the stuff you can see.

[Cheese]

including information about your printer

 

 

 

 

.....no, i am not kidding

[Emit]

all i know is lp's don't work for me anymore

[Resol]

1. Last login date

2. Amount of times logged in / usage

3. Other alias's currently being used (machine ID / IP match)

 

I had a few names I had to register again, but there were from an old computer I had not used in years, that was set up on a different IP.