Bounty Hunter Archive
Thread: A TIMELINE CORRECT, JEDI-FREE SERVER OPTION?
mikeymonkey wrote:
This is pretty pathetic.
YOU WOULD BE OUT OF A JOB.
And if you hunt Jedi out of real life hate for them, then please, step away from the computer, walk outside, and get some fresh air.
Message Edited by Draxie on 07-28-2005 02:00 PM
It's not going to happen - maintaining the seperate code would be a nightmare for SOE with all the updates, and I don't think the Jedi code has an easy off switch after being in the codebase over a year.
The only way I could see this happening is voluntarily - move to the lightest pop server, and have every player ban Jedi from everything they can. Designate the unofficial Jedi free server.
It's not going to happen - maintaining the seperate code would be a nightmare for SOE with all the updates, and I don't think the Jedi code has an easy off switch after being in the codebase over a year.
The only way I could see this happening is voluntarily - move to the lightest pop server, and have every player ban Jedi from everything they can. Designate the unofficial Jedi free server.
Lol it is easy just turn off the viilage or set the phase time to 10 years. No FS village no Jedi.
mikeymonkey wrote:
This is pretty pathetic.
YOU WOULD BE OUT OF A JOB.
And if you hunt Jedi out of real life hate for them, then please, step away from the computer, walk outside, and get some fresh air.
you idiot. I'm out of a job as of the last publish.
but, yeah....I'd pay the $100 to be on a jedi-free server. Jeezums if such a place were for real you wouldn't have to move me ... I'd grind all new characters!
Coder and ex-build engineer myself - and believe me, there is nothing that will make QA scream worse than having a non-uniform code base. They don't like one-offs for the simple reason that it increases their workload, and if some bug gets through it's their ass on the line.
They could work around it by having the jedi on/off switch as DB driven (databases being seperate for each server), but a responsible QA department would then still have twice as many test cases for each patch, testing if the new content works with both jedi on and off. QA is a major cost in software, so I really don't see SOE taking on a huge cost for a change that negatively impacts their marketing spearhead of the jedi. So again, my opinion is a jedi free server is never going to happen.
The player base, like I said before, could easily force one through server culture. Go to the least populated server, and have players agree not to group with, not to help in any way, and to ban every jedi ever seen. It wouldn't ensure a jedi free server, but the visibility problem would go way down.
Message Edited by ProzacRefugee on 07-28-2005 07:19 PM
This is EXACTLY waht I have been championing!
AWESOME idea.
I would pay more to play on a server like this.
I also love to see how many players seemed to be threatoned by it - LOL
YES YES YES
ProzacRefugee wrote:
TheMadCoder the issue isn't if it can be done - of course it could. But SOE isn't going to want to switch that bit is the truth - not just to please the jedi, but because introducing special behavior for a single server means somebody has to manage it, somebody has to remember to make the special update EVERY patch for that server so that bit is still off, and (most importantly)that server now has to be tested on it's own EVERY time.
Coder and ex-build engineer myself - and believe me, there is nothing that will make QA scream worse than having a non-uniform code base. They don't like one-offs for the simple reason that it increases their workload, and if some bug gets through it's their ass on the line.
They could work around it by having the jedi on/off switch as DB driven (databases being seperate for each server), but a responsible QA department would then still have twice as many test cases for each patch, testing if the new content works with both jedi on and off. QA is a major cost in software, so I really don't see SOE taking on a huge cost for a change that negatively impacts their marketing spearhead of the jedi. So again, my opinion is a jedi free server is never going to happen.
The player base, like I said before, could easily force one through server culture. Go to the least populated server, and have players agree not to group with, not to help in any way, and to ban every jedi ever seen. It wouldn't ensure a jedi free server, but the visibility problem would go way down.
Message Edited by ProzacRefugee on 07-28-2005 07:19 PM
Oh, I have no doubt that manager two code-bases is more difficult that one, but I can't think of any game that doesn't have different rulesets for differing servers (except for games like AO, which when one server cluster gets over-populated, they add another - up to 3 now.)
Almost everygame Ihave playedhas PvPand/or PvE servers.
UO has Siege Perilous (& Mujen,) a cluster with the exact gameplay, but completely different ruleset compared to the other 20+ servers they run. Yes, it has its problems every time a patch hits the servers, but it's there to keep the VETS playing.
Again, it is totally possible to implement this - but like I said testing will be the bottleneck, and right now SOE can't even put out Publishes without bugs for one system, much less 2. Part of this might be they need some better internal tools - from what TH was describing their bugs wind up being transported some of the way on Excel spreadsheets. Regardless, I don't see SOE putting more pressure on QA for a task which will flow directly in the direction of their marketing, even if that marketing is ultimately a bad idea.