Search results

Will do some more tests with an old Q6600. This CPU is more than 8 years old and should be a good reference for stone age PCs. The freezing might happen during the screenshot process. "If cpu 2 core 2.4ghz" Why people try to play games with office pcs?

Btw. is AutoHotKey detected by Rustbuster?

I think publishing a players full IP address is not a nice way. At least you could obfuscate the last digits.

Because Vsync is activated in Rust?

I wonder if its now possible to change the Stack Size.

A lot of RustBuster Players got banned by RustBuster Client 1.4.6 with the message: "RustBuster Detected Hacks. Found an unknown hack. 7801" This is a false positive. It is recommended to unban these Players manually (via /rbunban) or to wipe the banlist (The ini file, and do /unbanall and a...

This problem started when the Client 1.4.6 was released. Had to disable RustBuster on the server. I wonder if its possible to add an option to RustBuster that it only makes screenshots and does not actively checks for hacks, in case of something like this happens.

@DreTaX Found an unknown hack. 7801 is a massive problem. Some legit players cant join the server because of this.

Suddenly got a bunch of people being banned for "RustBuster Detected Hacks Found an unknown hack. 7801" What exactly is this number 7801 for?

The problem is when UAC is completly disabled on your PC. Therefore the rust client will be in an infinite start loop. UAC is mandatory. @DreTaX I wonder if its possible to check for RustBuster if UAC is even activated and simply skip the admin check if its disabled.

"Rustproofing at Rustbuster" Best product advertisement ever for Rustbuster

Found the reason I guess, it affects all servers and can be easily exploited. @DreTaX contact me asap on Skype.

No idea why this happens. The logs are all normal. Also since I use RustBuster my CPU load increased massively. Before it was 25%, now the rust server is using all 2 cores with only 3 active players and 20k objects. It needs even more resources than my Rust Experimental Server. The server...

Literally unplayable because of that spelling bug.

The code is fine. I also don't get it why its not working. I haven't found any reliable decay tool yet. Is the decay function of "Wiper" reliable?

Yeah I did that. I attached a compiled Fougerite version.

Yeah, I found the problem its the Server.FindPlayer() function. https://github.com/fougerite/Fougerite/blob/c3a10d86f07f08185d0d761a9a87b67c77b8ee87/Fougerite/Fougerite/Server.cs#L202-L206 It only accepts SteamIDs starting with 7656119 LuaEmu 1.9.7 uses ids starting with 7656120 for some reason

I'm not sure why this is happening. With the latest LumaEmu version 1.9.7 a player is unable to teleport to another players. If Player1 sends a request to Player2 and Player2 accepts the request he (Player2) will receive the message "Player isn't online!" This problem does not exist when...

Can you post the error which is inside the Log file of fougerite?

I never had this error with RustPP / Fougerite and I'm running a Fougerite server for over a year. Do you use a different ulink version?