![]() Here's what checks I suggest to add/improve the combat check. Ban count for rather outdated cheat implementations: YES.So i am not sure if i should really go for the pain of providing something initial, if the next thing that happens is a (paid? +) obfuscated/secret spin-off thing. Still i'm not sure with the community, all these methods need a lot of testing, and people may not want to share their secrets - it's already similar with paid configurations, but also with 'good configurations' someone made. I would invite people to contribute rather, provided i'm not in dire need of money and go for monetizing all over. Thinking of pattern detection (and possibly machine learning), i would put such entirely server side, if i wanted it.Apart from the trap-nature, entities resemble detecting patterns of behavior rather, but doing this with such a strong client-side thing doesn't seem to make sense to me, because client code is running on the client, and cheat client code will be able to distinguish.There are gray zones and Minecraft keeps adding weird stuff, but that's the basic direction i took here. Reason being that we're free + open source + low resource developer-wise, so we/i prefer methods that provide some kind of lasting protection rather. Entites means posing traps for cheat implementations to fall for, while the principles of direction for NCP rather mean to find envelopes to fit around vanilla behavior.Entites made complex will stress the server.Apart from being bypassed by less-simple made clients, entities are client-side and as such pose a major potential for annoyance :).A somewhat older rant/page i made is here: I will be happy to test any betas of the check.Įssentially it can be bypassed easily and will be bypassed in generic ways, so it doesn''t pay long term. I think the community will extremely appreciate the KillAura-Bot check. Heres what I imagine the config to look like: įeedback is appreciated. Such as one hit is equal to one violation level. I think thic can be customizable in the action section. If a player hits that bot too many times in a row or in certain amount of time, action will be taken. ![]() ![]() Every now and then the bot may pop in front of the player during pvp. Depending on their looking direction, the bot will move and adjust. A bot floats around a player while they're playing. I'm sure you already know and have seen this check but here's a explanation on how I see and how I think it should work. ( Spigot Page) ( GitHub) Since this project is open-source, I think you guys can at least get a good idea on how the KillAura-Bot check works. NTAC is now currently abandoned and is open-source. I used to use NTAC alongside NoCheatPlus for KillAura checks. It won't solve all KillAura hacks but it will put a dent into them. A bot should spawn spawn next to a player and check how many times a player hits that bot. I am proposing that a KillAura check be added. Yet, there is still a major flaw in NoCheatPlus, and that's KillAura. Once I have perfected the config, I wish to discuss the potential of the config in future versions. localautosettings load my_server_config.This is not an issue, this is a enhancement request.Īfter taking on the challenge of making a community config ( here), I have really come to appreciate the work that has gone into NoCheatPlus and the respect I have for keeping it free and active. You replace with the name of the configuration file you want to load.Īn application example would look like this. If it is, you can reapply it with the load sub-command. To restore a configuration you or someone else has previously saved, make sure that the corresponding file is located in the settings folder. If you want to share your configuration with a particular person, you can send him the created file, which he can then store in his settings folder and load with the load sub-command explained below. If you are using LiquidBounce 1.8.9 and have not changed the default installation path, it should be located in %appdata%/.minecraft/LiquidBounce-1.8/settings under Windows. This file will be saved locally on your hard disk in the LiquidBounce folder. localautosettings save you can save your current configuration in a file with the specified name. Just like the command for regular AutoSettings, it also has various sub-commands, which are explained in the following. The command that makes all this possible is. ![]() To make this possible, LiquidBounce supports a feature called LocalAutoSettings, which allows you to save your current configuration in a file which you can reload at any time or share with the rest of the community. ![]() In addition to the possibility to load configurations from our official repository, it is also possible to create your own and save them locally for later use. Contribute to this page on GitHub Local AutoSettings ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |