2
Compatibility
Changes
This version adds a config folder. After you upload the jar and restart it should just create an Awesome guns folder and in it will be 3 folders.
Makeing guns/ammo: To create new guns just go into GunsConfig and make a new yaml file and you can call it whatever I would start by copying one of the defaults for a easier time. Some key notes are that the command to get the item will be /ag (disName), the ammo needs to be the itemName of the ammo you want it to be, and things like effects cannot be null you will have to put in an effect but you can just make the duration 0.
Nuke config: another new item is the nuke, this config file is the only one that needs to be nammed Nuke.yml you CANNOT change this it will not work if you do.
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:rnxveBcM:FoJzdGyW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rnxveBcM:FoJzdGyW"
}

