tutorial:modding_tips
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
tutorial:modding_tips [2019/07/24 13:08] – added "Applying changes without restarting Minecraft" fudge | tutorial:modding_tips [2019/08/19 19:39] – [PitFalls] PitFalls -> Pitfalls jamieswhiteshirt | ||
---|---|---|---|
Line 22: | Line 22: | ||
* 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 ===== | ||
- | ===== Applying changes without restarting Minecraft ===== | + | * Don't import |
- | Restarting Minecraft can take a hefty amount of time. Thankfully, there are tools that allow you to some apply changes while the game is running. | + | |
- | ==== Reload changed classes ==== | + | |
- | In Eclipse | + | |
- | do '' | + | |
- | Note: this only allows you to change method bodies. If you do any other kind of change, You will have to restart. | + | |
- | However, if you use [[http://dcevm.github.io/ | + | |
- | ==== Reload textures ==== | + | |
- | After you make a change in a texture ('' | + |
tutorial/modding_tips.txt · Last modified: 2024/04/15 02:25 by solidblock