We're introducing Carbon for client, which is a tool designed to allow developers to go wild and explore Rust client-side features and communicate with the server.
This repository is designed to allow doing as much as possible that's not player client distructive as things can go crazy very quickly. Some of the following features are planned and not yet implemented.
- Load custom content (AssetBundles); audio, 3d models, shaders, materials, textures.
- Create custom entities & item definitions which are then synchronized with the server.
- Properly clean up when disconnecting from a server.
Currently, the main downside is that it is basically impossible to properly protect the client & server with Anti-Cheat, since these are memory modifications which Rust's anti-cheat disallows running Rust when Carbon for client is loaded. One other downside is the way it's shipped and the way you can enable/disable Carbon for client.
Unzip the release patch in the root of your client.
Very important to note: run RustClient.exe and not through Steam or Rust.exe. Nothing bad will happen, it'll just not start, by throwing this error:
Once everything's set up and installed, when launching RustClient.exe, you'll be welcomed with this console window, which will do its initial processing before actually launching the client.
Carbon for client uses Roslyn to compile c-sharp files found in BepInEx/carbon to execute code on the client on the fly. (Subject to change)
To create your developing environment using Rust client's assemblies, reference everything from BepInEx\interop, BepInEx\core and BepInEx\plugins.
To be able to connect to any regular Anti-Cheat-enabled servers, all you need to do is remove the winhttp.dll that can be found in the Rust client folder when Carbon for client is present. I advise moving that file in any other directory than root of the client.
For a full uninstallation, all you need to do is delete the following folders/files: BepInEx, .doorstop_version, dotnet, doorstop_config.ini.
This project is not designed for hacking or any exploitative behavior of any sorts. It's designed to be used by creative limited communities that want to explore the expanded limits of Rust client-side modding.