ModListReporter Plugin
ModListReporter is a useful mod for Minecraft that allows the server to receive information about the list of installed mods and resource packs on the client. The mod automatically sends data to the server when the player connects, allowing the server to
1
Compatibility
Changes
ModListReporter is a useful mod for Minecraft that allows the server to receive information about the list of installed mods and resource packs on the client. The mod automatically sends data to the server when the player connects, allowing the server to keep track of the mods and resource packs being used.
Features: Automatic Data Transmission: The mod automatically sends the list of installed mods and resource packs to the server upon player connection. Compatible with Fabric: The mod is designed to work with Fabric API and is compatible with Minecraft version 1.20.2. Server Logging: The server plugin logs the received data and saves it to text files for further analysis. Text File Creation: The lists of mods and resource packs are saved in separate text files, organized by player name and connection time. Requirements: Client: Fabric API for Minecraft 1.20.2. Server: Paper 1.20.2 with the ModListReceiver server plugin installed. Installation: For Client:
Download and install Fabric API for Minecraft 1.20.2. Place the ModListReporter-1.0.0.jar file into your Minecraft client's mods folder. For Server:
Ensure your server is running on Paper 1.20.2. Copy the ModListReceiver-1.0.0.jar file into your server's plugins folder. Restart the server to activate the plugin. Usage: After installing the mod and plugin, each time a player connects to the server, their list of mods and resource packs will be automatically sent to the server. The server will log the received data and save it to text files in the plugins/ModListReceiver/modlists folder.
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:xhM92boE:4jgZWI01"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xhM92boE:4jgZWI01"
}
