Bukkit

@kangarkooo

Every client-side thing can be bypassed though :p.

Concerning block breal speeds, just tell us if theres false positives - in fact our orientation is rather the fastest breaking time (usually the latest), we don't distinguish MC versions there.

Concerning walls + entity-interaction/fighting: The problem again is latency, as with direction + reach. We don't know which past-position of the targeted entity the attacking player was trying to hit, assume at least the target to be moving. In the usual case there is air everywhere, but with many obstacles it could get very difficult to ever hit anyone, if we don't implement more advanced methods than just raytracing. We do have all the ray-tracing code in place, so it's not the problem to add this in general. In fact we already maintain a location trace for the past so and so moves, so we will (eventually...) check direction and reach versus that trace, based on some timing- or latency-window mechanics+constraints at least for players and estimate if the target could have been hit. Once we have that implemented, i think we could also check ray-tracing for blocks. This will avoid checking for 60 past moves (...) taxing the server a lot, and we also don't just check the current location of the target, to prevent not being able to hit in situations with multiple obstacles, e.g. with lots of pilars. So this has to wait for direction+reach using the location trace (both pass = check ray-tracing).

Not sure this was a good explanation, but it's kind of planned :).

@kangarkooo

We don't check if attacks go through walls.

Concerning the checks working or not working, i assume the kill-aura will send the necessary events to make the plugins believe the player is turning towards the aims and attacking, just like a skilled player might do it. Freecam mode or looking elsewhere does not mean anything there.

While they can activate kill-aura, it should be strongly limited already, otherwise they'd get huge amounts of improbable + angle + direction etc. alerts. They usually adapt to what NCP is checking for, so you can't judge by being able to activate it and have it fight al ittle bit.

The checks are configured for some balance between false psoitives and strictness on cheaters. You do have the possibility to alter some parts, like penalty timings, how fast they can turn, frequencies, i suggest you have a look at the documentation pages about fight checks and combined checks (yawrate, improbable).

Now the interesting question is, what it can achieve. Hitting through walls (nearby) unfortunately is still possible, but what else is there that skilled players couldn't do? Don't expect to fully block it, plugins spawning fake entities will probably soon get bypassed in generic ways, so you end up with confining instead of blocking again.

@MyPictures

@BrutalNetwork

Apart from blockinteract.... you also have blockbreak checks of course (frequence, fastbreak, reach, direction). Which checks did you disable or can post/send your config for simplicity?

@kristijan260393

Realistically i would rather enable donations or payed services if i needed it for survival mode. We still do have some basic cost for keeping hold of some domain and other, so donations or even some payed extras are not 100% off the table. Don't expect the core to become private too easily though...

@kangarkooo

Good :), the logs might be lengthy, most interesting might be what happens just before logout and just after login, until/from first teleport(s).

@kangarkooo

Do you have logs of log-out locations or are the log-in locations logged before AuthME teleports players?

If you can reproduce it locally or with very few players online, you can add "debug: true" to the moving section of the config of NCP (or even above in the checks section), which could give more hints about what happens, but it'll spam the logs for each and every player, so it's usually not an option for production servers.

@kangarkooo

Do you have the bukkit.yml set to use exact login locations? Do you have a plugin enforcing login locations related to last logout (not suggesting to have one in general though)?

@kangarkooo

I don't know - are the issues with NCP + cancelling ender-pearl teleport or in general? There could be something like the "inexact spawn position", but i can't tell by now.

@UnwrittenPaper

Please cut that part and use a paste, e.g. http://dev.bukkit.org/paste/ with language set to "text only", for better readability, thanks :).

Could it be you were using a plugin-manager plugin to reload NCP? Some are incompatible and in general it's dangerous ...

Otherwise: Can you post the full output of the "ncp version" command too (and /cncp if available)? What permissions plugin are you using?

@AlterEgo1337

What do you mean by "have more fly hackers"?

• Are more people flying?
• Are ther more alerts about fly moving/fly checks?

What does "updated" mean?

• Do you use a server-mod version that is just 1.7.10, or does it also support 1.8 clients?

@Theepwner

Thanks for the reference, hope we can test/reproduce.