Tags
Creators
Details
1.0.0-1.20.1
Compatibility
Changes
First Version of Kami Votes!
kami-vote-mod-1.20.x
Welcome to the kami-vote-mod-1.20.x plugin! This plugin is designed to display vote links for your Fabric website in Minecraft. It offers a range of customization options, and we're excited to add more based on your feedback.
How It Works
-
Installation
- Place the mod file into your server's
modsdirectory.
- Place the mod file into your server's
-
Configuration
- Upon loading the mod, it will generate a JSON configuration file in the config folder. This file allows you to customize various aspects of the
/votecommand. - You can modify the colors, styling, and text displayed by the command.
- Upon loading the mod, it will generate a JSON configuration file in the config folder. This file allows you to customize various aspects of the
-
Adding Links
- Open the generated JSON file and add your vote links under the
Linksarray.
- Open the generated JSON file and add your vote links under the
-
Reloading Configuration
- Use the command
/vote reloadto apply any changes made to the configuration file. Note that this command requires admin permissions.
- Use the command
-
Usage
- Players can use the
/votecommand to view the list of links you have configured.
- Players can use the
Customization Options
- Colors and Styling: Customize the appearance of the text and links.
- Text: Modify the message displayed before the links.
- Dynamic Links: The plugin supports a dynamic number of links, adapting based on your configuration.
Future Updates
We plan to expand the customization options and features based on user suggestions. Stay tuned for future updates!
Support
If you encounter any issues or have suggestions, please reach out through Discord #ladicius.
Thank you for using kami-vote-mod!
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:cMDA6CFo:tkr8uSaH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cMDA6CFo:tkr8uSaH"
}

