tutorial:modding_tips
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
modding:tips [2019/01/22 19:44] – asie | tutorial:modding_tips [2024/03/28 22:43] – Add javax.swing to the packages that don't work well on all systems earthcomputer | ||
---|---|---|---|
Line 8: | Line 8: | ||
* Block.Settings -> FabricBlockSettings | * Block.Settings -> FabricBlockSettings | ||
* EntityType.Builder -> FabricEntityTypeBuilder | * EntityType.Builder -> FabricEntityTypeBuilder | ||
- | * While an official configuration system is being worked on, one replacement for now is to use Java .properties or JSON. | ||
* For a built-in resource pack or data pack, please ensure that an " | * For a built-in resource pack or data pack, please ensure that an " | ||
===== Mixins ===== | ===== Mixins ===== | ||
- | * To modify | + | * To cast a class to an interface it doesn' |
- | * @Redirect and @ModifyConstant mixins cannot currently be nested (applied by more than one mod in the same area at the same time). This might change later in development - however, for now, alongside @Overwrite, please avoid them if possible (or discuss bringing the hook over to Fabric' | + | * @Redirect and @ModifyConstant mixins cannot currently be nested (applied by more than one mod in the same area at the same time). This might change later in development - however, for now, alongside @Overwrite, please avoid them if possible (or discuss bringing the hook over to Fabric' |
- | * If you're adding custom fields or methods, | + | * If you're adding |
===== Networking ===== | ===== Networking ===== | ||
* Packets always begin execution on the **network thread**, however accesses to most Minecraft things are not thread-safe. In general, if you're not exactly sure what you're doing, you want to parse the packet on the network thread (read all the values out), then use the **task queue** to perform additional operations on the **main server/ | * Packets always begin execution on the **network thread**, however accesses to most Minecraft things are not thread-safe. In general, if you're not exactly sure what you're doing, you want to parse the packet on the network thread (read all the values out), then use the **task queue** to perform additional operations on the **main server/ | ||
+ | |||
+ | ===== Pitfalls ===== | ||
+ | |||
+ | * Avoid using the '' |
tutorial/modding_tips.txt · Last modified: 2024/04/15 02:25 by solidblock