0 Members and 3 Guests are viewing this topic.
I respect MM's position as creator of Soldat giving him the final say in these matters but he explicitly says he doesn't really care. Personally I think that someone with a more current interest in this community should decide. Letting flab decide would be the most sensible course of action in my opinion. Sorry but I simply don't believe these excuses.
maybe he could let the beta team decide ?
Quote from: skn0fx on July 02, 2009, 07:56:10 ammaybe he could let the beta team decide ?lol that would be quite a dumb idea.In my opinion Flieslikeabrick should decide what to do here, and whether to add a new developer alongside Enesce if he is staying as dev.
Quote from: Poop on July 02, 2009, 07:59:43 amQuote from: skn0fx on July 02, 2009, 07:56:10 ammaybe he could let the beta team decide ?lol that would be quite a dumb idea.In my opinion Flieslikeabrick should decide what to do here, and whether to add a new developer alongside Enesce if he is staying as dev.I agree, because FLAB is the next guy from MM.
<SpiltCoffee> I have one more question, EnEsCe...<SpiltCoffee> EnEsCe: "It still doesn't explain why the "forgotten fix" was only enabled on his server. If it was forgotten there, it should have happened on all servers, not just his."<SpiltCoffee> Would that be because you work on two versions, the development version and the official version, and you take stuff that works from the development version over to the official version?<EnEsCe> didnt I say it was left in because that code only compiles on the dev version?<SpiltCoffee> Well, people are still thinking "well, if it appeared in the development version for 2 years, why hasn't it appeared anywhere else?"<SpiltCoffee> I think because most people believe the dev version is the exact base for what eventually is released<SpiltCoffee> Is that the case?<EnEsCe> that sounds abit dumb, how could they expect a development version to appear anywhere other than the developers server?<SpiltCoffee> Hang on, I'll get another quote<SpiltCoffee> lol<SpiltCoffee> You're not getting me yet<SpiltCoffee> "How is it possible that you somehow remembered to remove the ping code for every server release, but it somehow "accidentally" managed to stay in your binary for this long? If what you said was true, the ping code would've been enabled for ALL servers or NO servers at all. But it was only enabled on yours, so it's obvious to me that this was no accident. Furthermore, this whole ping issue has been in your attention for month<SpiltCoffee> s, probably over half a year, and it's only now that you suddenly find the code causing this after you're caught red handed. Isn't that a bit too convenient."<EnEsCe> introduce them to compiler directives<SpiltCoffee> Eh, that'll do for an answer, I guess...
Quote from: truup on July 02, 2009, 07:30:10 amAlso, no comment on MM's post, anyone can see through the message..oh yes, I see pretty well
Also, no comment on MM's post, anyone can see through the message..
Quote<SpiltCoffee> I have one more question, EnEsCe...<SpiltCoffee> EnEsCe: "It still doesn't explain why the "forgotten fix" was only enabled on his server. If it was forgotten there, it should have happened on all servers, not just his."<SpiltCoffee> Would that be because you work on two versions, the development version and the official version, and you take stuff that works from the development version over to the official version?<EnEsCe> didnt I say it was left in because that code only compiles on the dev version?<SpiltCoffee> Well, people are still thinking "well, if it appeared in the development version for 2 years, why hasn't it appeared anywhere else?"<SpiltCoffee> I think because most people believe the dev version is the exact base for what eventually is released<SpiltCoffee> Is that the case?<EnEsCe> that sounds abit dumb, how could they expect a development version to appear anywhere other than the developers server?<SpiltCoffee> Hang on, I'll get another quote<SpiltCoffee> lol<SpiltCoffee> You're not getting me yet<SpiltCoffee> "How is it possible that you somehow remembered to remove the ping code for every server release, but it somehow "accidentally" managed to stay in your binary for this long? If what you said was true, the ping code would've been enabled for ALL servers or NO servers at all. But it was only enabled on yours, so it's obvious to me that this was no accident. Furthermore, this whole ping issue has been in your attention for month<SpiltCoffee> s, probably over half a year, and it's only now that you suddenly find the code causing this after you're caught red handed. Isn't that a bit too convenient."<EnEsCe> introduce them to compiler directives<SpiltCoffee> Eh, that'll do for an answer, I guess...Just (an attempt of) an answer to those wondering why it's only his servers being affected if he forgot about it...
EnEsCe: As some of you know, [almost] every time I have released a dedicated server there has been some debug stuff that I forgot to remove upon release (Most notably lines in console).
<mafioza> <mafioza> i did test it tho<mafioza> <mafioza> i ran a server straight from ssh<mafioza> <mafioza> my ping was 100<mafioza> <mafioza> from php commander<mafioza> <mafioza> 50<mafioza> <EnEsCe> yep<mafioza> <EnEsCe> soldatmonitor?<mafioza> <mafioza> what about it<mafioza> <EnEsCe> I mean were you running with soldatmonitor<mafioza> <mafioza> no<mafioza> <mafioza> just regular<mafioza> <EnEsCe> mk
And even if he does use compiler directives to hide the code from public releases (which would still be intentionally, not by accident), don't forget that there are other proof to back up the claim. He's been aware of this issue for a long time (because mafioza told mentioned it), so it's obvious that EnEsCe knew about the lowered ping only on his server. If it was by accident, he would've looked into it then, which he didn't for obvious reasons.
Quote from: Geoffrey on July 02, 2009, 07:45:52 amI respect MM's position as creator of Soldat giving him the final say in these matters but he explicitly says he doesn't really care. Personally I think that someone with a more current interest in this community should decide. Letting flab decide would be the most sensible course of action in my opinion. Sorry but I simply don't believe these excuses.However, as he said, what really matters is that there is progress. This issue must have delayed the coming of 1.5.1 and will continue delaying if it goes on any further, that isn't very good. So instead of continuing to talk about this, we should just move on.Be appreciative of the free stuff. You normally don't deserve them in the first place.
Quote from: MetsuriTossavainen on July 02, 2009, 08:09:52 amQuote from: Poop on July 02, 2009, 07:59:43 amQuote from: skn0fx on July 02, 2009, 07:56:10 ammaybe he could let the beta team decide ?lol that would be quite a dumb idea.In my opinion Flieslikeabrick should decide what to do here, and whether to add a new developer alongside Enesce if he is staying as dev.I agree, because FLAB is the next guy from MM.Don't push flab too much even if he probably should decide, Great responsibility usually just leads to trouble..
MM's reply is sad.. "because really I don't care"You've let me down.
You're honestly going to say that we should ignore all NSC has done because we're "delaying" the release of 1.5.1? I expected something more intelligent from you, STM.
Also if it was a fix, why would you reduce it from the actual variable that is used to calculate the ping, instead of just using the reduced value in the corresponding algorithm, eg:Code: [Select]bullet_trail(PingTicks-2);vsCode: [Select]PingTicks -= 2;bullet_trail(PingTicks);The former would be more logical "fix" attempt.
bullet_trail(PingTicks-2);
PingTicks -= 2;bullet_trail(PingTicks);