1.2.9
Compatibility
Changes
Latest changelog:
-proper removal of data.
-thunderstorm now takes longer to start based on amount of players on the server.
1.2.7:
-online and offline(still holding) player data is cleared on natural rain or thunderstorms; this also applies to commands like /weather rain|thunder or /weather clear, being used or spammed.
1.2.5:
-Less RAM usage per saved player data
-Some calculations of player values are multithreaded.
-Fixed potential memory leaks.
-Player data is deleted 2 minutes after logging out
-Bug fixes & many features and improvements
Breakdown of update 1.2.0:
-
Data is stored for each individual player and can track their values, mod is now runnable on both client-side(Singleplayer) and server-side(Multiplayer, not fully tested).
-
If player is sitting in a boat random value is added to counter each tick,
-
If player stands up from a boat random value is decreased from counter each tick.
-
If player has been out from a boat for at least 1<->2(countdown) minutes counter will fully reset to 0.
-
If counter reaches it's goal the thunder will soon trigger no matter if player is in a boat or not.
-
While thunder is active counters of all players are reset and will not start filling up until thunder is over.
-
Counters are able to fill up only in overworld and on a sea level.
-
Data for individual player is reset upon logging in to a server.
-
Counters are attached per player, which means 1 player needs to reach goal for thunder to start, having multiple players in a boat won't speed up the process.
-
In this update player is no longer needed to sit in a boat all the time.
-
Everything is randomized.
Not recommended on large servers!
Coded in Eclipse IDE.
PORTS:
1.14.4 <-> 1.15.2
1.16.5
1.17.1
1.18.2
1.19.2 <-> 1.19.4
1.20.1 <-> 1.20.4
1.20.6 <-> 1.21.4
1.21.6 <-> 1.21.8
1.21.9 <-> 1.21.10
1.21.11
26.2
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:EfJ3d5iI:MMqJ15sM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EfJ3d5iI:MMqJ15sM"
}

