Included content
| Name | |
|---|---|
This update primarily focuses on the mod's code structure and organization, but has some extra features and changes as well.
This update also resolves a pesky lag spike that kept taking place, and that went un-noticed by me.
You killed %s %s is now shown as Killed: %s%s killed you %s time(s) is now shown as Died to: %sclient-guiSmoothScroll config propertylang/translation texts to implement support for their modded mob stats
StatType's ID is yeetinator:times_yeeted;
yeetinator:times_yeeted: 32.betterstats.stattype_phrase.[stat_id_namespace].[stat_id_path] translation key syntax."betterstats.stattype_phrase.yeetinator.times_yeeted": "Times yeeted"Times yeeted: 32Search textbox on the filters panel now has a placeholder text that says Search.... This should tell the user more clearly that the black rectangle is in fact, a search textbox.fabric.mod.json, so as to avoid depending on "platform-specific" code. Plus the Fabric Loader API for reading fabric.mod.json data isn't even as flexible as I wanted it to be.
properties.json, which can be found inside of the mod's .jar file.Given how Minecraft now works, Items can now dynamically have their corresponding ItemGroups changed. In the past, each Item had a "set" ItemGroup that'd stay as-is forever. Now, items can change groups depending on the world settings.
Where a performance issue now came in is;
1.20.4 as far as I could observe), and this instead takes place when opening your inventory for the first timeBy making the process of assigning item groups to items take place right after the world loading process, rather than when opening inventory.
Because it was affecting this mod as well actually.
As you may have noticed, this mod's "Item stats" tab shows items grouped into item groups.
For this to happen however, the game needs to have already arranged the items into groups.
And so what I did in the past is, I made the game do that process whenever the betterstats screen is opened, not realizing this causes lag spikes on large mod-packs.
As such, I have decided that it's best to just make the game do the whole process as the world is loading, rather than making the user sit thru lag spikes during gameplay.
| Name | |
|---|---|
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.
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:n6PXGAoM:wyQ2nH56"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:n6PXGAoM:wyQ2nH56"
}