Carbineer Archive
Thread: The Devs alegances are revealed
InfluenzaSWTA
Mon Jun 14, 2004 12:53 am
#14
Re: mounts. Probably because it's a much harder problem to solve than the scatter hits.
Kaelle_DB wrote:
It wasn't just the "other scatter hits" that were ignoring toughness, and defensive mods,scattershot was doing it too. All we wanted was the combat log to be fixed, which was the source of that problem. Yes the next two publishes are about the jedi blah, blah, blah this issue was reported in beta. If it could be hotfixed on a sunday when it became a problem to the jedi, it could have been added to a publish long ago.
You're right, I didn't realize ScatterShot was also doing it. But my point still stands: there are countless issues that need to be resolved, and there always will be. As long as the only problem with scatter hits was the combat spam being reported incorrectly, well, then they weren't going to get fixed for a long time. But once they seriously start impeding a group of players who are the focus of a monthly publish, then it's time to fix it.
novamarine
Mon Jun 14, 2004 7:28 am
#15
Bennyboy4308 wrote:
Wow, thats angrifying.
ROFL 
Please stop being so melodramaculous. 
jfang
Mon Jun 14, 2004 7:29 am
#16
I am not supporting the devs, nor do I necessarily believe that this was a wise course of action (I have my own views on the prudence of not fixing the scatter bug before, fixing it now, and the revamp schedules). I also do not know the extent of the scatter shot, what it affected on TC2, or how and when it was fixed. This is just my attempt at guessing what happened behind the scenes, and why this might not be as bad as it looked.
Very possibly, they released the jedi revamp first because they wanted to test a how the new system might work before the big combat revamp. Because the combat revamp affects so much, it is very hard to get right. However, if they put some aspects of it into jedi in PvE combat, they can sandbox test a few issues and gain insight into what is acting as expected and not acting as expected.
As for fixing scatter shot 2, this was probably political in nature. They probably figured out what was going on with it a while ago. However, since (1) it was already in the game and people knew about it, used it, and compensated for it, (2) it was not game breaking, and (3) the combat revamp was coming up, it wasn't worth fixing. If they changed it there would undoubtably be many people (such as fencers and teras kasi) complaining about it. Furthermore, "what's two more months of waiting" for the combat revamp.
This issue became much more pressing with the jedi publish. If they want to argue that jedi are more or less done for the near future, number 2 becomes much more important. A jedi in theory should be much better than several "regular" combat classes, and if a MBH-carbineer can use some bug to kill them, this is a significant problem to their claim. This is exacerbated by the fact that there are many more BH's than jedi on live servers, many of which openly claim to have the sole goal of killing (and sometimes even griefing) jedi. A problem like this would undoubtably be taken advantage of until fixed.
As for why it was hot fixed on a Sunday, there is very little time to test patch 10 (this is 10, right) before it goes live. I think there is another 5 days according to the original schedule (I'm not sure of that either). In this light, one day of testing, especially one weekend day of testing, is vital to the timeline. If they had another month it would likely have been fixed at a more leisurely pace. However, on Test Center, all patches are hot-fixes (so that's not that big a deal, this fix isn't *that* special), and in an active testing cycle, hours of testing make a difference.
TAfirehawk
Mon Jun 14, 2004 7:32 am
#17
JorahRamsai wrote:
Entire jedi population, a whole 50 people per galaxy.
InfluenzaSWTA wrote:
La di da.
Maybe you aren't aware of this, but Publish 9 is all about Jedi. How can you get mad that they're fixing bugs that would otherwise DECIMATE the entire Jedi population? This is a great sign that the Devs are paying attention to the big issues and fixing them while they're still on Test.
50 my arse......I don't get around THAT much and I know of at least 25 on Chilastra and I KNOW there are TONS more....
Most servers have 100-200 EASY.....
jfang
Mon Jun 14, 2004 7:42 am
#19
TAfirehawk wrote:
And one more thing, let me have my **edit** session....
Hmm?
/emote re-reads posts by TAfirehawk in this thread...
Hmm again? I have no idea what you mean... Unless you are referring to the up and coming "Carbineer Revamp" (we can hope, right 
)
Edit: By the way, TAfirehawk, any idea why the post I am quoting (right above this one) is darker than the other ones? The background is a hair darker (and matches the left "user information" box) than all the other posts... Odd...
Message Edited by jfang on 06-14-2004 10:43 AM
TAfirehawk
Mon Jun 14, 2004 7:46 am
#20
Posts all look the same to me, none are darker on my screen....
jfang
Mon Jun 14, 2004 8:28 am
#21
Hmm, that's odd. It does noton my screen too now.
Annoying forums. Either be broken or working and stay that way. Stop flipping between the two.
TAfirehawk
Mon Jun 14, 2004 8:29 am
#22
jfang wrote:
Hmm, that's odd. It does noton my screen too now.
Annoying forums. Either be broken or working and stay that way. Stop flipping between the two.
LOL
Like the entire login service being down for 8+ hours this morning.....gotta love Lithium.....
jfang
Mon Jun 14, 2004 8:49 am
#23
TAfirehawk wrote:
gotta love Lithium.....
That can be taken in so many ways... 
Does anybody elsefind it odd that they named the engine "Lithium".
Kaelle_DB
Mon Jun 14, 2004 10:02 am
#25
jfang wrote:
I am not supporting the devs, nor do I necessarily believe that this was a wise course of action (I have my own views on the prudence of not fixing the scatter bug before, fixing it now, and the revamp schedules). I also do not know the extent of the scatter shot, what it affected on TC2, or how and when it was fixed. This is just my attempt at guessing what happened behind the scenes, and why this might not be as bad as it looked.
I agree that it did need to be fixed and I'm not pissed at the devs for fixing it. I could down any jedi faster than another jedi could using scattershot 2.
The thing that pissed me off was the gap between the way bugs affecting jediwere treatedand how those that affect the rest of the professions are treated. We carbineers have have a hard time getting our bugs acknowIedged, let alone fixed, no matter how many times we /bug or post. I'm just jealous of those damn spoiled jedis. Ihad a jedi tell me friday, with full confidence, that it would be fixed ASAP.
I'm not angry at the devs for fixing jedi bugs in the context of a jedi publish. It's more the whole idea of the 2 jedi publishes that gets me more. I don't see why a profession that isn't even garaunteed to players and who's population is a very, very, very small fraction of the player base, should recieve more attention then the professions that are garaunteed to people who buy the game and that are supposed to be working right out of the box.
It's the devs failure to fix the really simple things that could have huge positive effects on professions that make me mad. I really didn't care that much about the scattershot log bug, it really wasn't that big of a bug. But how hard would it be to add +15 or +20 speed to carbineer? Or fix our ham costs?How hard is it to add +25 polearm accuracy at master with some added polearm toughness? A 10 year old who has never played the game could look at the bonuses for the melee professions and see that pikemen are lacking. These things could have been done so easilly long ago. There are tons of examples for every profession, very easy things to fix that vastly limit that profession's potential. At launch commando was uncerted for nearly all of it's weapons and the wepons couldn't even be made on any of the servers because they required very specific resources that hadn't spawned, they couldn't even get heavy weapons xp because the launcher pistol, their one working weapon, gave them pistol xp. It tookso long to"fix" the commandos, fix being a relative term, that their correspondent actually quit the game. The devs weren't even responding to his emails he said.
It's in contrast to these sort of things that that fix irked me.
Message Edited by Kaelle_DB on 06-14-2004 10:03 AM
TAfirehawk
Mon Jun 14, 2004 10:18 am
#26
Very good points.....
This is like the straw that broke the camels back.....it just wasn't ONE straw
And this is my point about the Devs don't learn from past mistakes, the problems just keep piling up.....
/stirpot
/continuebiatchsession