|
Developer Chat Logs Once a month, on the second Saturday, at 7PM EST, we will hold an open Developer discussion on IRC. The logs from these chats will be posted here. |
|
Thread Tools | Rate Thread | Display Modes |
#151
|
||||
|
||||
Kendrick
you fail
__________________
|
#152
|
|||
|
|||
Can this be removed yet? I'd like to be able to play without spending 10 minutes being teleported to the same spot over and over.
|
#153
|
||||
|
||||
Quote:
Be careful what you wish for... (in this case demand)
__________________
SWGEmu Support Helper
SWGEmu is a non-profit, open source community project SWGEmu OR Project Status List... New Community Member FAQ... Bug Tracker... How to install SWGEmu... |
#154
|
|||
|
|||
Can it be tweaked, fixed, and upgraded BEFORE putting it on the server and forgetting about it? Since that's the major thing. If the devs are so adament about keeping it, fine. Remove it, fix it, put it back up. If it still doesn't work, remove it. There is simply NO excuse for putting up a faulty code and leaving it for two weeks while the entire testing process suffers dramatically because of it. There is just no excuse at all for that.
|
#155
|
||||
|
||||
I think it is probably being tweaked on ITC, but the one running on TC will remain active to prevent any attempt of future speed hacking, until it is replaced by a tested and more advanced version. I think.
__________________
SWGEmu Support Helper
SWGEmu is a non-profit, open source community project SWGEmu OR Project Status List... New Community Member FAQ... Bug Tracker... How to install SWGEmu... |
#156
|
||||
|
||||
This is something that is not going away but it isn't just put up on TC and forgotten.
Quote:
Can we please stop doing this? -->>>
__________________
Odwill SWGEmu Test Center Director Odwill@swgemu.com | EmuIrc | Helpful Links SWGEmu -e- Support Support@swgemu.com SWGEmu is a non-profit, open source community project. |
#157
|
|||
|
|||
Depends, is the fixed version on the TC? Is everyone still suffering from a broken anti-hack? If so, then no, we can't stop. As I have said, if it's being worked on, GREAT, but until it's ready remove this broken one. There's no excuse to keep it up and make the ENTIRE community suffering, the very process of testing itself suffering from this. It aint like you have to worry about people speed-hacking in the time before the revised version is finished. Cuz even if they do, two words (or is it three?) DATABASE WIPE. So the hackers getting a couple days/weeks of freedom really doesn't matter, since in the end everything we do will be wiped. However in that time everyone else will be able to move normally. I have yet to see any sort of justification to keep the broken code on the server until the revised code is finished.
|
#158
|
|||
|
|||
I'm not suffering. Honestly, I don't think the Devs need any justification. I think they have a better handle on development than you do.
__________________
I thought what I'd do was, I'd pretend I was one of those deaf-mutes, or should I? |
#159
|
|||
|
|||
Then they can continue to listen to, not just myself, but countless people ***** and moan because they're being rubberbanded back and forth hundreds of meters like a goddamn rag-doll. Obviously they have no responsibility to listen to us, and most of the time they shouldn't. But rubberbanding is impeding testing, maybe you don't suffer from it but hundreds of others do. When ignoring the community causes testing to suffer, that's just wrong.
|
#160
|
|||
|
|||
Well if you are so steadfast about 'testing' yet you afk macro which is a whole other kettle of fish..... My suggestion would be to come back after the OR and all these problems will be a thing of the past.
EDIT: Especially when you admit you don't even report bugs, that is the job of the debugger....
__________________
I thought what I'd do was, I'd pretend I was one of those deaf-mutes, or should I? Last edited by Lobreeze; 10-26-2009 at 09:09 PM. |
#161
|
|||
|
|||
Quote:
|
#162
|
|||
|
|||
And I quote Cilraaz
Quote:
Quote:
I'm not arguing, I'm making very valid points.
__________________
I thought what I'd do was, I'd pretend I was one of those deaf-mutes, or should I? Last edited by Lobreeze; 10-26-2009 at 09:48 PM. |
#163
|
|||
|
|||
That response hardly says I don't report bugs, it just points out the flaw of saying a debugger doesn't detect bugs. And afk grinding DOES constitutes as testing, why? Because I'm doing it ingame. ANYTHING done ingame is testing. Every. Single. Little. Thing. is testing, simply because it's done on the server. My afk-grinding could potentially reveal a serious flaw of some sort that'd be picked up by the debugger (or reported by me when I noticed it) which would lead to it getting fixed. The point is, you don't know what bugs are out there waiting to be found, so any action, no matter what, is testing.
|
#164
|
|||
|
|||
Quote from policy;
Quote:
__________________
I thought what I'd do was, I'd pretend I was one of those deaf-mutes, or should I? |
#165
|
|||
|
|||
Quote:
|
|
|