BlossomBridge 2.1.0 | Standalone

2.1.0 had one goal: make the project available across any project.

Changes:

1. The API is no longer a mod, but a library that can be used in any Java or Kotlin project.
   1. It no longer has mod metadata (such as an id, name, version, etc.), and won't be loaded by any mod loader.
   2. Jankson is now "included" using the api keyword in the build script.
2. The deprecation of BasicConfigClassKt is now marked as DeprecationLevel.ERROR. If you haven't migrated to the new Java equivalent yet, do so. Will be fully removed in the next patch when possible.
3. LoggingHandler now has methods to get the current Logger instances.
4. LoggingHandler is now capable of running vararg log methods, to make full use of SLF4J.

---

Full updating guide: https://docs.tiazzz.me/BlossomBridge/latest/developers/updating
Full Changelog: 2.0.2...2.1.0

---

Note

The sources file might be janked out because it's only the Kotlin sources or something (I ran kotlinSourcesJar and called it a day)

BlossomBridge 2.0.2 for 1.19.2+

2.0.2 again focused mainly on fixing minor flaws the 2.0.0 update had, updating is suggested, but take note of the problems 2.0.0 serves.

Patches:

1. The Kotlin BasicConfigClass isn't serializable or something by Jankson, so it was replaced with a Java class.

Full updating guide: https://docs.tiazzz.me/BlossomBridge/latest/developers/updating
Full Changelog: 2.0.1...2.0.2

BlossomBridge 2.0.1 for 1.19.2+

2.0.1 focused mainly on fixing minor flaws the 2.0.0 update had, updating is suggested, but take note of the problems 2.0.0 serves.

Patches:

1. Wrongly formatted MC version dependency in fabric.mod.json.
2. ConfigManager.getConfig() is not null safe, while it used to be before the Kotlin rewrite.
   (oh the irony)

Full updating guide: https://docs.tiazzz.me/BlossomBridge/latest/developers/updating
Full Changelog: 2.0.0...2.0.1

BlossomBridge 2.0.0 for 1.19.2+

Warning

This update has breaking changes. It is suggested to update and take precautions.

Warning

This release may be unstable in some situations, if you do end up having problems, report them at the GitHub issue tracker.
We will soon try to release a more stable version if needed.

Changes:

1. Changed codebase to Kotlin.
2. Made LoggingHandler.literalDebug() always ignore config.
3. Made ConfigManager.loadConfig() also run saveConfig() after validation.
4. Removed main package in favor of a very plain ModInitializer object.
5. AbstractConfigClass -> BasicConfigClass (Renamed)
6. net.tywrapstudios.blossombridge -> org.tywrapstudios.blossombridge (Renamed)

Tip

With this update, we added a documentation site, check it out some time!

---

Full updating guide: https://docs.tiazzz.me/BlossomBridge/2.0.0/developers/updating (hopefully)
Full Changelog: 1.1.1...2.0.0

BlossomBridge 1.1.1 for 1.19.2+

Full Changelog: 1.1.0...1.1.1

BlossomBridge 1.1.0 for 1.19.2+

Full Changelog: 1.0.3...1.1.0

BlossomBridge 1.0.3 for 1.19.2+

• Added a proper README.
• Added some plain Logging to ConfigManager.
• Properly documented ConfigManager$getConfigJsonAsString().

Full Changelog: 1.0.2...1.0.3

BlossomBridge 1.0.2 for 1.19.2+

• Added validate logic for AbstractConfig.
• Slightly tweaked the try-catch logic in ConfigManager$load().
• Added ConfigManager$getConfigJsonAsString().
• Improved Javadoc for Sources (a sources jar will be available for this release.)
• Fixed the main part actually crashing in on itself, as it threw InvalidConfigFileException because the file name was appended .json and not .json5.

---

Smaller note:
I hope that Jitpack works now that I made a release (tag), because sadly it keeps failing to build the branch, and already kept failing 1.0.1. I don't really know why, because a jitpack.yml file is clearly there and is set up perfectly fine.
If it does not work, just use Gradle's files function to import the library.
In this example I made a libs directory in the project root directory and put the main- and sources-jar in it, then you simply define blossombridge_version as 1.0.2 (blossombridge_version=1.0.2) in your gradle.properties and it works!

dependencies {
	// To change the versions see the gradle.properties file
	minecraft "com.mojang:minecraft:${project.minecraft_version}"
	mappings "net.fabricmc:yarn:${project.yarn_mappings}:v2"
	modImplementation "net.fabricmc:fabric-loader:${project.loader_version}"

	// Fabric API. This is technically optional, but you probably want it anyway.
	modImplementation "net.fabricmc.fabric-api:fabric-api:${project.fabric_version}"
	// BlossomBridge
	modImplementation files("libs/blossombridge-${project.blossombridge_version}.jar")
}

BlossomBridge 1.0.1 for 1.19.2+

• Added JitPack Stuff, hopefully

Full Changelog: 1.0.0...1.0.1

BlossomBridge 1.0.0 for 1.19.2+

• Config System
• LoggingHandlers