Test Server Feedback

tl;dr - Everything mentioned below is in development, not in testing. That's the only truly important part of the message below.

Word to who made ya',

I've grown tired of people approaching me on IRC asking me to reactivate their SISI account, or retrieve their password. Not because I'm a hatefilled slacker but because it is sensitive information and should go through a well defined process that I am not a part of. But that well defined process is somewhat stupid and relies on manual input from both you as well as us. Seeing as we want as many people on SISI testing our stuff, for functional feedback and bug reports, this sounds like a silly barrier of entry to create. It also prevents new players from accessing SISI between our full mirrors and although they are less likely to do that they should still be able to do so if they want (if only to use SISI as the worlds most over-engineered EFT clone). So automating some account information migration from TQ to SISI sounds like a goood idea that would simplify the process for you guys, remove the need for us to have QA people constantly monitoring this forum thread and generally allow more people access to SISI.

So I started poking at things and getting feedback from involved parties, mostly through Twitter and here in the office. As it stands I'm certain I can very readily supply changes to already existing user accounts, password information and what characters they have access to (and some other stuff that you guys don't care about but would be nice for internal processes). This is mostly possible because all this information is clearly sperated from any in-game simulation affecting data. Things such as skill training, character creation, manufacturing and other obvious nice to have scenarios create a whole lot of data all over the database, using unique indentifiers as relational keys between them and these identifiers might very well have been used on SISI already due to people playing there. Furthermore, the prospect of dealing with things such as "Character A on server X training Engineering 1 while character A on server Y is training Electronics 2. Servery Y training finishes and should be reflected on X etc.". Not saying these problems are impossible to overcome but they are less than trivial and I'm not wasting time on solving them for the purpose of the current scope of the project. If they were trivial I wouldn't be spending time on this.. there would be a builtin incremental merge mirroring solution in the DB engine already.

As I'd very much like to see this project help new players getting onto SISI I'd very much want to see new user creation reflected on SISI. As I mentioned above this would (probably) not (god why did I add that probably there.. now everyone thinkgs this is going to happen) include the character created due to all the item data a character creation involves and the possibility of itemID conflicts between TQ and SISI. But at least creating the user over there should be very much possible.

So there you have it, no more asking for SISI reactivations at least. Hopefully no more waiting for new mirrors for new accounts either! Feedback and suggestions welcome here and at @CCP_PrismX. Please direct any complaints, trollings or hatefilled rants to my specific inbox for that.

You were able to understand what he meant, Aswell as everyone else. Who cares?

I don't get it - are you planning to seperate the 2 servers completely (no more mirrors) or are you planning on making the server able to use the live account data?

You made my day!

He spelled separated wrong so I'm inclined just to snicker at his affront to my typos

That's the plan as things stand.

soon™ (also known as "Some time between yesterday and the heat death of the universe. Sorry I can't be more specific." - CCP Greyscale)

Remember me Prism? I had that bug I could never log in after a mirror... Happens again.

Actually, I was the 2nd like...Don't say things that you know NOTHING about... anyway, I wonder how this will change the way people share accounts on sisi

Finished internally last week. One of those things that are rather hard to test and as I'm going on vacation this Friday it probably wont go live until August.