Announcing Tremulous, Unlagged! (1.1.2)

[WolfWings ShadowFlight]

Unlagged Tremulous w/ TJW + DenyBuild patches based on SVN 829 codebase, runs on all 1.1.0 servers, no SVN required. Download disabled. Passed the code along to Kevlarman to rebuild into something suitable for public dissemenation. I proved it worked, he can make you all happy with how the code is presented.

Patch Recipe (hard too apply minor repair seamless step)
Tremulous SVN Revision 829
TJW's patch against SVN Revision 823
Location for Building Messages and Deny/AllowBuild patches
Unlagged 2.01 Source Code
Unlagged 2.01 Patching Instructions and details

Downside, it requires a 150k client-side download. Upside, well, it's only 150k and a one-time download at that.

Quick tip: cg_projectileNudge, set that to roughly your ping. Round to the nearest 10ms, no need to be exact. Lucifer and Pulse Rifles will suddenly be a lot less of a threat since you'll be able to see where the bolts actually are, and dodge around them. We were having 400pingers from Australia dodging my 50ms PR blasts, and vice-versa. It works. :-)

Seperately, cl_timenudge -30 won't make players jerky when they move around anymore. Set it, live it, love it.

Beyond that, I can also attest that it made a 400ms Dragoon a threat to me, Mr. 50ms, when I had a shotgun and helmet and armor. But get used to aiming at the target, don't aim ahead of them like you use to. Stick that gunbarrel right on top of them and pull the trigger.

[Caveman]

Thanks for the Mod, could please make the source available?

[WolfWings ShadowFlight]

Not yet, no. Working to convert it into patches to submit to the primary SVN repository for Tremulous instead if they'll accept them.

[vcxzet]

add it to bugzilla first
then they can decide

[Stof]

No, you'll give the source code now since you are breaking the GPL licence by not doing so :evil:

PS : I can't wait to test that

[yetshi]

there is a huge difference between this and normal servers.

i had 160 - 200+ ping and it was faster than my regular <30 ping

[Caveman]

Not yet, no. Working to convert it into patches to submit to the primary SVN repository for Tremulous instead if they'll accept them.

Then please remove the binary also.
You have to distribute the source alongside the binary.

[stalefries]

How would I go about setting that setting? This looks real nice, I could use an advantage over pr's.

[benplaut]

Please release the source, as you're required to, and us linux users are being left out in the cold.
Will these patches even work with linux, for that matter?

[WolfWings ShadowFlight]

As you wish. Removed.

[WolfWings ShadowFlight]

Please release the source, as you're required to, and us linux users are being left out in the cold.
Will these patches even work with linux, for that matter?

And how are linux users being left out in the cold? The .QVM's are the only files that run on Mac, Linux, and Windows without recompiling.

[The Reverend]

Ok so i downloaded the patch/mod what exactly do I have to do with it to make it work?  Just put it in my tremulous base folder??  Please elabborate for people who have no clue as to what to do with it.  Like me.    

THX

[PHREAK]

Finally, antilag for Tremulous.
BTW, he doesnt have to release the code unless he wants to be included in the official version.
The beauty of GPL is that anny add-ons don't have to be GPL.
Read the licence.

[WolfWings ShadowFlight]

Finally, antilag for Tremulous.
BTW, he doesnt have to release the code unless he wants to be included in the official version.
The beauty of GPL is that anny add-ons don't have to be GPL.
Read the licence.

Not quite. If I release the binaries (.QVM's in this case) I do have to release the code, but all I did was apply a stack of patches (though most of them by hand) which was why I didn't want to release my direct code-tree since I'll be submitting it for inclusion into mainline trem.

[pyrax]

Wewt!

I'll be putting this in right away.  Thanks, double-double-u.

edit: if I knew how

[Paradox]

Make it automatic, not every player wants to have to configure things like this.

[WolfWings ShadowFlight]

Make it automatic, not every player wants to have to configure things like this.

The two settings I quote are optional. By default it tries to stay equivilant with stock Trem for how it acts client-side, and some people prefer the settings at 0.

[Ksempac]

Make it automatic, not every player wants to have to configure things like this.

When i tried it on WW's server, i didnt know about the 2 commands and it worked well without them
so thats not a real problem even if you dont know them

[Paradox]

Wont this reap a whole new series of abuse, people setting their settins at ridiculous levels so they see luci shots way before?

[kevlarman]

Wont this reap a whole new series of abuse, people setting their settins at ridiculous levels so they see luci shots way before?

not really, you can't see a luci shot before it has been fired, and anyone can see where it is going, so it doesn't really help to dodge it, the only thing it would do is make luci shots act unpredictably close to the one firing it.

[WolfWings ShadowFlight]

Wont this reap a whole new series of abuse, people setting their settins at ridiculous levels so they see luci shots way before?

And beyond what Kevlar has said, if you set the value too high it will push the lucifer and pulse rifle shots 'up against the nearest wall' instead of leaving them in mid-air. So at best you'll have a warning on the wall behind your head from 'abusing' this setting. It doesn't make things any easier to dodge, it just tells you were it'll land, NOT where it'll travel if set too high.

[raanan]

Wont this reap a whole new series of abuse, people setting their settins at ridiculous levels so they see luci shots way before?

It doesn't make things any easier to dodge, it just tells you were it'll land, NOT where it'll travel if set too high.

And that's what crosshairs are for

Considering I don't really want to spend alot of time repatching anything or figuring out how to patch in the first place, will I see any benefit from messing with those commands you listed even though I won't have your patches?

[WolfWings ShadowFlight]

And that's what crosshairs are for

Considering I don't really want to spend alot of time repatching anything or figuring out how to patch in the first place, will I see any benefit from messing with those commands you listed even though I won't have your patches?

Actually this is talking about other players watching your shots. :-)

And cl_timenudge can help without the Unlagged patch, projectileNudge doesn't exist without Unlagged.

[vcxzet]

Unlagged Tremulous w/ TJW + DenyBuild patches based on SVN 829 codebase, runs on all 1.1.0 servers, no SVN required. Download disabled. Passed the code along to Kevlarman to rebuild into something suitable for public dissemenation. I proved it worked, he can make you all happy with how the code is presented.

Patch Recipe (hard too apply minor repair seamless step)
Tremulous SVN Revision 829
TJW's patch against SVN Revision 823
Location for Building Messages and Deny/AllowBuild patches
Unlagged 2.01 Source Code
Unlagged 2.01 Patching Instructions and details

Imho you need to give source code of your implementation of unlagged to comply with GPL
edit: doh! sorry I need to read before hitting submit

[Stof]

It's true, if all you did was apply a few patches, you should have said so in the download, and you should have given the user the way to get the patches himself.

Now, since you also had to make some more manual changes, you shouldn't have released the QVM without your modifications according to the GPL.



Anyway, it is really isn't too important and that patch looks really promising. Just don't take too much time in giving the source code or the FSF will come after you :wink:

[Vector_Matt]

...

Awesome, thank you so much. GJ!
I can hardly wait for it to be included with the release.

[WolfWings ShadowFlight]

Unlagged Tremulous w/ TJW + DenyBuild patches based on SVN 829 codebase, runs on all 1.1.0 servers, no SVN required. Download disabled. Passed the code along to Kevlarman to rebuild into something suitable for public dissemenation. I proved it worked, he can make you all happy with how the code is presented.

Imho you need to give source code of your implementation of unlagged to comply with GPL
edit: doh! sorry I need to read before hitting submit

Except, what you think doesn't matter. The reality is that I need to supply compatable source code for what I did, and I pointed direct, exhaustive links to the changes I made so far as I know and can recall. Just because you don't believe I haven't fulfilled the spirit of the GPL, doesn't mean I haven't fulfilled the letter of the GPL.

[WolfWings ShadowFlight]

It's true, if all you did was apply a few patches, you should have said so in the download, and you should have given the user the way to get the patches himself.

Now, since you also had to make some more manual changes, you shouldn't have released the QVM without your modifications according to the GPL.

Anyway, it is really isn't too important and that patch looks really promising. Just don't take too much time in giving the source code or the FSF will come after you :wink:

Again, incorrect. The only 'manual changes' I had to make were applying the Unlagged patch, since it doesn't come in .patch format. Applying the patch involves reading a large document and following it step by step using the Mark 1 Eyeball and Mark 1 Human Brain instead of an x86 CPU to apply the patch automagically. It is still, in the end, only a patch I applied and downloaded.

And I never claimed I invented the code. Not once. Even a cursory Google search would have indicated why I was so religiously saying I was adding Unlagged to Tremulous, not saying I was adding anti-lag features. I was importing a patch for a specific implementation of anti-lag, Unlagged 2.01. Said so numerous times, and even in the initial post I said it had Unlagged added. It's not my fault you didn't investigate enough to understand I wasn't just capitalizing the word to be cute, so don't you dare lay the blame at my doorstep for your failure you follow up wih research before making blind claims.

[next_ghost]

Except, what you think doesn't matter. The reality is that I need to supply compatable source code for what I did, and I pointed direct, exhaustive links to the changes I made so far as I know and can recall. Just because you don't believe I haven't fulfilled the spirit of the GPL, doesn't mean I haven't fulfilled the letter of the GPL.

From http://gpl-violations.org/faq/vendor-faq.html:

What are common mistakes ?
...
- Including the wrong version of the source code. The source code has to be 1:1 corresponding to the executable (object) code actually shipped.

If those patches don't apply cleanly together, you should make and distribute single complete patch which does.

[PIE]

Applying the patch involves reading a large document and following it step by step

Rediculously large and unnesessarily detailed document.. thats all fine and dandy but what if I don't care how it works and don't want to waste an hour reading all of that?

I don't see any "this is how to apply" anywhere.. you can't expect the average person to sit through that... or me for that matter.. how do you apply this.. short sweet step by step abridged idiots version..