1.0.0
Compatibility
Changes
1.0.0 Beta release- SprayMods Very First Public Version
Releases
-The SprayMod Library HUD- This includes the Spray Library, Settings and Editor -The SprayMod Spray HUD- This allows you to select a "Flex" or "Spray"
The Editor HUD overhaul
The Editor HUD recived a massive overhaul from its very first version before 1.0.0 -From 12 Pre selected colours there are now Hue custom colours introduced into the Editor. -Imports- Import a .PNG into the editor allows you to edit it into your own "Spray". -Saves- Save a custom spray into whatever name you want. This saves automatically and any other name will have (2), (3) and so on. -Shortcuts- Custom shortcuts are now introduced to add a new feature into the mod. This allows you to use all the tools without pressing the buttons.
The Settings HUD introduction
The settings HUD was introduced into the Mod to add customisation into our mod. The settings introduced: -Spray sound -Spray sound length -Cooldown display -Display options: -Message above hotbar -Progress bar -countdown numbers -Spray wheel animation -Placement Preview -Wheel centre Display -Wheel visual settings -Tinted background -Slot numbers -Custom Spray folder -Wheel opening animation -A Spray Wheel opening delay
FLEXES
"Flexes" are animated objects such as the 4 pre installed in Version 1.0.0. These are: Grass block, Sword, TNT and Ice block. Each animated to add satisfaction and a new feature.
MULTIPLAYER
People with the mod can see "Sprays" or "Flexes" Used by you INSIDE LAN worlds Sound effects and visualisation are still in development.
As from SprayMod version 1.0.0 This is still a beta Version so there will be Bugs and features not released YET.
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:LZOv3TKf:sSgPdH76"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LZOv3TKf:sSgPdH76"
}

