Admin Notice: Server testing #6

[Cannon]

After a disasterous start I finally got flhook update 6 running on the server. It turns out my programming is even worse than my college grades suggest.

This update has the following changes:
- Autoban on repeated cheat detection (like we used to have about 2 years ago)
- Some other cheat detection stuff
- A fix for missions breaking the server
- Shields are dropped when somebody F1s/disconnects. The system should also stop their ship but this didn't work.
- Hook controlled AI bot test code

To do next:
- Find out why ships sometimes drift so much. The should drift based on the amount of time they have been disconnected. The expected rate is 1 meter per second of disconnect time up with a maximum of 50k in the y-axis and 1/10th of that in the x and z axis.
- Find all instances of the problem that caused the "disasterous start" and fix them.
- Try to stop a ship in space if the player disconnects/F1s.
- Try to stop the crash when I unload the player control plugin while the server is running (i.e. the last dropped spanner incident).

Some people have asked why am I testing this stuff on the server. There are multiple reasons:
- I'm doing this before 4.86 comes out so that I can be reasonably sure the FLHook part of 4.86 is stable.
- Real players using the software are much better testers than me.
- There are some good features I can add to the server before 4.86 comes out. Stay tuned for these.

---

Proud member of "the most paranoid group of people in the community"

Old Avatar #2 | Old Avatar #3

[mwerte]

- Hook controlled AI bot test code

To do next:
- Find out why ships sometimes drift so much. The should drift based on the amount of time they have been disconnected. The expected rate is 1 meter per second of disconnect time up with a maximum of 50k in the y-axis and 1/10th of that in the x and z axis.

AI bot test code? Mind expanding on that or is it anti-cheat stuff?

Thanks for the anti-F1 measures.

I -think- that the drift is caused by someone F1ing while moving. The server goes "guy was moving, but not getting an update from the client, so let's extrapolate". Don't know why it speeds up/goes in random directions though.

And I agree with doing tests on the server. We are much better at breaking things then you are.

Thanks for the new tweaks!

---

[Panzer]

Can we has NPC spawn ban again?

---

[Veygaar]

Cannon is amazing:Dprops for all of this

---

Veygaar for Admin Moderator 2013!!!

[Anonymous User]

AI-code-test-whut?

---

]

[hribek]

To do next:
- Find out why ships sometimes drift so much. The should drift based on the amount of time they have been disconnected. The expected rate is 1 meter per second of disconnect time up with a maximum of 50k in the y-axis and 1/10th of that in the x and z axis.

Perhaps because the physics prediction engine assumes constant acceleration, not constant velocity. Meaning the best time to F1 and be invulnerable is right after you apply thrust - be it thruster, cruise engine, or strafing. If you time it right, the ship drifts away very quickly.

AI-code-test-whut?

Come back when you're sober.

[Stuart.croll]

I've always thought the F1 drift was a time related thing

---

[Anonymous User]

.
Come back when you're sober.

I am... I'm always.

just dun get what this thing is...

---

]

[AeternusDoleo]

- Find out why ships sometimes drift so much. The should drift based on the amount of time they have been disconnected. The expected rate is 1 meter per second of disconnect time up with a maximum of 50k in the y-axis and 1/10th of that in the x and z axis.

Simple. No player object left to test collisions once you move out of a certain range. Few NPCs or miscellaneous objects bump you to get you to an idiotic speed, clientside inertia governing is gone, so you simply move at whatever speed those NPCs give you. And since NPCs are immune to inertia and collisions with players... it's like being hit by a baseball bat. Repeatedly. Homerun swing to the edge of the system.

Not sure if it's possible, but the same state craft are on when in their final docking approach with bases (invulnerable, no shields, impossible to change course due to collisions or by commands) might be appropriate for players who F1'd. Minus the invulnerable of course. Then after setting that, set the speed to 0, and you should end up with a ship that is locked down in mid-space.

---

Wide awake in a world that sleeps, enduring thoughts, enduring scenes. The knowledge of what is yet to come.
From a time when all seems lost, from a dead man to a world, without restraint, unafraid and free.

Mostly retired Discovery member. May still visit from time to time.

[Vladimir]

It would be great if we had the drifting exeption for barges in guard systems, because logging it in and moving some 40k back to base is really evil, and docking with that thing is evil too.

---