MikeZA

Sorry, can't help myself, stupid people are so fun to play with :rolleyes:

Yes, this was quite obvious, but why are you interrupting again?

Can we expect cleaner patching from now on? Or will I be bitching about amateur code again in the next patch? You know, the stuff that looks like its written by a child and tested by a monkey...? Maybe the 'verbal abuse' will drive the point home. Edit: fixed epic spelling fail

You have very poor comprehension, don't you mate. I do not associate myself with the kind of work the dev team releases. If you know half a shit about coding for a living you would understand this. Why are you interrupting a conversion between people who actually know what they are talking about?

What, in another 5 weeks when the next half-assed patch is rushed into release?

Another reason not to want to be associated with the dev team. Poor expectation management and rushed patching. It is better to release half a patch than a half-assed patch.

Either they knew it would not work and released it anyway, or they did not bother to test it at all. Both of those reasons are sufficient for me to avoid any sort of association with their work. Just that simple. I have also noted that the only people defending this issue are fanboys, where are these devs? Why don't they respond? Do they not have an explanation? Smells like not giving a shit to me... And the fix is not rocket science: remove the code until you figure out how to accurately and consistently determine a player's velocity in real-time. Christ, I do not believe I actually had to say it...

I didn't think it would be necessary to point out.. but okay... I was pointing out why this patch is bad to someone who thought otherwise, not find out why the devs don't give a shit and release poor code. The reason for THAT is pretty obvious to me. I have never released code that I knew would not work. Not wanting to be associated with a team that does so is not smugness, that is me being a professional. Not my fault people can't tell the difference. And a follow on: if they didn't know it wouldn't work... did they not TEST it? You know, like professionals do it?

If the devs gave a shit they would not have included code in the patch that the KNEW would not work properly. Not backing down on something is not the same as being unreasonable. Maybe I have not heard anything to change my mind? All I have heard is STFU or GTFO from fanboys instead of having someone who actually knows half a shit about the subject give me a valid reason for the inclusion of this code. I will not be debating inclusion of bad code with people who are obviously ignorant regarding coding at a commercial release level. I don't try teaching monkeys physics either.

And for the smart-asses who think me not contributing to the alpha code actually means anything:

Please, as if you could afford my billable rate.

Not sure what the removal of 50 cals has anything to do with this post... I am busy upgrading my server back to 1.7.6 now, maybe in about 5 weeks 1.7.8 will be better... but probably not based on 1.7.7.

Not without being paid. Awww.... we have a thin skin, do we? Poor boy.

An you know what shepherds do to sheep, right?

I have only claimed to have one solutions and I have provided it above. Nice try at condescension, maybe next time you won't fail so hard at it. Besides which, why would I waste my time trying to teach the current developers when not to include code in a release when they are apparently unconcerned with their shit code's affect on the mod? That is like trying to teach a cat to read, the cat gives zero fucks about reading, so why bother?