documentation:fabric_loader
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
documentation:fabric_loader [2022/12/22 15:03] – Added a section on how to integrate Fabric loader into a separate game/app mchorse | documentation:fabric_loader [2023/12/27 12:57] (current) – ↷ Links adapted because of a move operation 194.190.81.32 | ||
---|---|---|---|
Line 86: | Line 86: | ||
// your dependencies... | // your dependencies... | ||
| | ||
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
- | implementation " | + | implementation " |
} | } | ||
</ | </ | ||
Line 101: | Line 101: | ||
==== Launching your app with Fabric Loader ==== | ==== Launching your app with Fabric Loader ==== | ||
- | If you've launched your app before through your own '' | + | If you've launched your app before through your own '' |
==== Setting up GameProvider ==== | ==== Setting up GameProvider ==== | ||
Line 115: | Line 115: | ||
=== Implementing GameProvider === | === Implementing GameProvider === | ||
- | For your game actually to launch, you to carefully implement **GameProvider** in a specific way. Here is a breakdown of each method does: | + | For your game actually to launch, you need to carefully implement **GameProvider** in a specific way. Here is a breakdown of each method does: |
* '' | * '' | ||
- | * '' | + | * '' |
* '' | * '' | ||
* '' | * '' | ||
* '' | * '' | ||
* '' | * '' | ||
- | * '' | + | * '' |
* '' | * '' | ||
* '' | * '' | ||
Line 130: | Line 130: | ||
* '' | * '' | ||
* '' | * '' | ||
- | * '' | + | * '' |
* '' | * '' | ||
- | For more information either consult the Fabric Loader' | + | An example |
<code java> | <code java> | ||
Line 262: | Line 262: | ||
</ | </ | ||
- | This class example assumes that argument '' | + | This class example assumes that argument '' |
==== Final touches ==== | ==== Final touches ==== | ||
Line 278: | Line 278: | ||
</ | </ | ||
- | That's a good sign. However, that's not it. | + | That's a good sign. However, that's not all. |
=== Initializing mods === | === Initializing mods === | ||
Line 324: | Line 324: | ||
</ | </ | ||
- | Then it's the root of the issue. To fix this, you need to add your App's jar, or folder (in development) to '' | + | Then it's the root of the issue. To fix this, you need to add your app's jar, or folder (in development) to '' |
<code java> | <code java> | ||
Line 338: | Line 338: | ||
this.jarFiles.add(" | this.jarFiles.add(" | ||
- | this.jarFiles.add(" | + | this.jarFiles.add(" |
} | } | ||
| | ||
Line 410: | Line 410: | ||
</ | </ | ||
- | After detecting the app's jar(s)/ | + | After detecting the app's jar(s)/ |
=== Loading mods from classpath === | === Loading mods from classpath === | ||
Line 416: | Line 416: | ||
If you're testing the mod from the submodule that has your app and Fabric Loader in the classpath, instead of compiling the mod and placing it into app's launch directory, for Fabric Loader to load your mod from classpath, you need to add '' | If you're testing the mod from the submodule that has your app and Fabric Loader in the classpath, instead of compiling the mod and placing it into app's launch directory, for Fabric Loader to load your mod from classpath, you need to add '' | ||
- | For more reference check out [[https:// | + | For more reference check out [[https:// |
documentation/fabric_loader.1671721435.txt.gz · Last modified: 2022/12/22 15:03 by mchorse