Tags
Creators
Details
0.9.0
Compatibility
Changes

RustyConnector
(Beta)
⚠️ DON'T UPDATE ⚠️
If you are starting a network from scratch feel free to dig into RustyConnector! If you are updating from v0.8 you should check the README under "Returning Features". You might be using features that have been removed and don't have a 1-to-1 re-implementation yet. To be clear ALL FEATURES FROM v0.8 ARE COMING TO version0.9 But the process will take time as we rewrite all of these features to work with the version0.9 rewrite.
⚠️ DON'T UPDATE ⚠️
🖥️ NEW API
version0.9 introduces a fully integrated Java API. You can start working with the version0.9 API right now:
repositories {
mavenCentral()
maven { url = "https://maven.mrnavastar.me/releases/" }
}
dependencies {
compileOnly 'group.aelysium.rustyconnector:core:0.9.0'
}
Changes
- Complete rewrite of entire software from the ground up.
- Native plugin system (called rc-modules)
- Fully-realized Java API
- Many "extra" features from v0.8 were removed and will be re-released as native modules, which users can install if they need those features again. (Check github README for updates)
- Users have the ability to reload specific units of the software without needing to reload the entire software.
- Integrated Database system (Haze) which allows you to use any database technology you want with any modules that use it. Module developers are able to support all concevable database technologies with ease.
- Virtual Family Servers on Velocity - All Families have their own virtual servers that get registered to the velocity proxy for compatability with non-RustyConnector systems. You can connect players to these virtual servers and the families will handle those connections.
- Non-UUID Server IDs - Servers default to using a new "<server-name>-<nanoID>" ID system for better readability. Users can adjust a setting in the server's config.yml if they want to use UUIDs for ids. Users are also allowed to directly edit the server.id if they want to implement their own id system.
Supplementary resources
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Hd02Faj9:nO8OCoU9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hd02Faj9:nO8OCoU9"
}

