![]() These mods/libraries must be deobfuscated to the development environment's mappings first. Mods (and libraries which use Minecraft code) are usually released as an SRG-obfuscated JAR, which prevents their direct use in development environments due to mismatch between SRG names from the mod/library and the MCP/mapped names in the development environment. Implementation "net.minecraftforge:eventbus:5.0.3" 'implementation' is for the main source set įor example, to declare a dependency on the net:minecraftforge:eventbus:5.0.3 library from the main source set: Soft dependencies usually take the form of isolated code dependencies, where the code that depends on the soft-dependency is isolated from the rest of the mod until the soft-dependency is detected as being present.Ī mod declares a dependency on a mod or library through Gradle, through the dependencies block. This often takes the form of cross-mod compatibility features, where a mod soft-depends on another mod or the mod's API. Hard dependencies should be declared using a dependency configuration to allow the Forge Mod Loader to detect the missing dependency and gracefully handle it by showing an error screen to the user, rather than the JVM crashing with a non-user-friendly exception message.Ī soft dependency is a dependency where the dependent mod does not require the dependency is present, but extra features or compatibility is added in the case of the dependency being present. This may be in the form of a code dependency, wherein the JVM will crash due to the missing class, field, or method from the dependency, or it may be in the form of a dependency configuration which mandates that the dependency is present. ![]() There are two types of mod dependencies: hard dependencies, and soft dependencies.Ī hard dependency is a dependency where the dependent mod requires that the dependency is present. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |