An updated code.lasthope.cs

The twist: Interpolate is client-side, and has nothing to do with server anything.

$net::interpolatetime parameter - client side - check.

function that uses the above parameter - client side - check

purpose of function - perform calculation on data supplied by the server.

It has all to do with the server everything.
 
Another slight tweak is available today. We kick for the new troc hack that is
making the rounds. I am using the test I should have been using all along.

http://home.tx.rr.com/bugs/lasthope2008.zip

I'll be taking a break from this for a bit to finish up the work on ReversePolate.

Ordinary "polate" is when a client sets interpolatetime to 0 and then their client
views all the motion of the other players with that setting.

ReversePolate is server side. The server may select a naughty player to be
reversepolated. If this occurs all players on the server will view the naughty
player's motion as if they all had interpolate set to 0 but only for the naughty
player. Every player's view of the other players will be unaffected.

There is more to be done here but thats the first step.
That is fucking retarded. What next, if someone plays with 120 FOV then everyone else will change to 120 FOV when they're looking at him?
 
Well that analogy sucks. Lets see if we can try a little harder.

Suppose the server detects someone using an autobeacon/shiva variant.

You are skiing along thinking you are safe behind the hills and blammo - the
heavy that couldn't see you somehow dropped a mortar right at your feet (again).

Since that heavy has beacons on top of everybody's head - what would happen
if you looked up and saw that the server had put a beacon over his head?
 
Useless. The polate thing is impossible to implement without a client-side update.

The idea, though, at all, is a gimmick. Just kick / ban. Why is that so difficult?
 
Well that analogy sucks. Lets see if we can try a little harder.

Suppose the server detects someone using an autobeacon/shiva variant.

You are skiing along thinking you are safe behind the hills and blammo - the
heavy that couldn't see you somehow dropped a mortar right at your feet (again).

Since that heavy has beacons on top of everybody's head - what would happen
if you looked up and saw that the server had put a beacon over his head?
Except interpolate doesn't make you see anything you couldn't see before, whereas autobeacon, and 120 FOV for that matter, does. So you should really be looking into this FOV thing first, it's much more of an advantage.
 
[amadeus tribes is dead amadeus]I hate the fact that people are able to change their FOV. OMG they can change their zoom FOV as well. People who turn off their weather to see better upset me as well. Clientprefs.cs was never meant to be modified.[/amadeus tribes is dead amadeus]
 
For those using the "log funny" capability of the lasthope2008 script
(or those that watch the "info" line of various players on sh-thole)
you may have noticed some players that got strange results.

We don't kick for strange results, we only kick for the results we know
are naughty. Strange results are just logged.

For a couple of years I have been tracking what I called "the Csitri group"
(sorry Csitri!). It was clear that they were not running stock 1.30 Tribes
or the 1.31 FoX variant because of what I call the "message-b" result.

Lasthope2008 looks at the version string in the Tribes data segment to see
if they are running 1.11 as this would be a bypassing signature.

These guys would return 467498966 for the message-b test and this did not
match anything I could find as legit OR bad.

On sh-thole we just tagged them as "msgb" or "mem msgb iff". The lasthope2008
script (if you turned on funny logging) would give you something like:

LH extra player endframe 11264009
LH extra player Gui hook 657045415
LH extra player iff-hook() 926566783
LH extra player message-b 467498966

LH extra player2 endframe 11264009
LH extra player2 Gui hook 286796199
LH extra player2 iff-hook() 926566783
LH extra player2 message-b 467498966

In frustration I caved and asked Andrew if he knew of any other "legitimate"
Tribes.exe's that were out there (Not 1.30 or 1.31). In this case I got
the dreaded brush off LOL!

Anyhow yesterday I was finally able to test and verify that these strange
results are actually legitimate. Awhile back Andrew had written a mem.dll
version of lasthope he called "1.35". The mem.dll changes the version
in the Tribes data segment to 1.35 and thats why the message-b result
comes out different.

This is why its important to be careful with strange results. "The Csitri
group" were not actually running a cheat configuration - in fact - they were
beta testers for an experimental anti-cheat written by Andrew!

Now if I can just get one of these "15g" guys to cough up their Tribes.exe
so I can clear up that mystery.
 
You will still be owned. While lasthope is disrespected by some and considered
obsolete - in the hands of a master it can still deliver a knockout blow. Beware.
 
Polate was among the best things to happen to tribes imo as it helped to level the playing field. The problem to me was that it was patched out rather than simply reducing cg damage, which would obviously make for the most level playing field. I'm not even sure that's a matter of opinion so much as fact.

C'est la vie!
 
Polate was among the best things to happen to tribes imo as it helped to level the playing field. The problem to me was that it was patched out rather than simply reducing cg damage, which would obviously make for the most level playing field. I'm not even sure that's a matter of opinion so much as fact.

C'est la vie!

This, but only if it was pre-1.11 or included with 1.11. Yes, 1.30 is recognized as a mod, but it doesn't alter gameplay ( datablock wise ). People would whine about reduced CG accuracy if it was implemented post-1.11 - just my opinion. Also you want BASE to appear to be BASE.
 
There was a brief time in SoA where people only had 30 CG bullets in LT, and it was awesome.

Of course whiners got rid of that fix too.
 
Back
Top