Why is it more infuriating than any other order?
Why isn't the 3rd spec released at the same time for all classes? I've never seen a game publisher give special privileges to 2-3 groups out of a dozen, months before other groups.
Rationally, do them all at the same time, throw them up on a test server, separate from the main server. Put a copy of everyone's character on the test server or use the same DB for both servers, but set the DB access on the test server for 'copy/update on write'. If you want to see early access and want to help NCSoft test, then play on the test server, but note -- any changes made on the test server won't be propagated back to the main server. The only benefit to players would be ability to see and learn new system (which may change if something is broken).
Have a fantasy "vendor" who can give you any type of currency and/or any level of item to your test character at no cost (*free*). The character and any items on the test server will disappear at the end of the test period. Once issues are worked out, release new binary to regular server and disable the test server. Once verified, archive or destroy test server & test world. There could be usefulness in rewarding an account-bound title associated with being a tester for the 3rd-spec release.
The test word would:
increase engagement of players
perhaps, attract new players.
Note, I'd only support character creation on the released/normal server. This would have the side effect of ensuring new players are registered and have a character created on the normal server, removing either of those being a "dissuader" of trying the new game after the test period.
If there is a need to test character creation, accounts would still be created/registered, first, in the 'current' game.
increase testing coverage beyond what is currently done.
Allow for simultaneous release of all classes
If "to-be-released" game info is to be dissuaded, then:
Ask testers not to leak, post or publish data about the new version, while, at the same time, realizing that such bans are all but guaranteed to not stop people talking about it.
In that light, I'd only take actions against those posting pre-release info. Even then, only action would be disabling their test account and disabling getting any accomplishment associated this event.
To make consequences "scale", I'd toss a ban on future participation for a time period of
6-months × Number_of_violations. One would hope people wouldn't get more than 1 violation. It's not perfect, no system is, but it's also meant to be low-maintenance/cost to implement/achieve.
Anyway, have said too much, so....end it here, except to add, sadly, that the current ordering may simply reflect its internal classID number based on the age of the class and the order in which the classes were released. ?