Skip to content

Loading philosophy

Olafcio1 edited this page Sep 28, 2026 · 4 revisions

§ Loading philosophy in the Avoid Framework


If you need access to the parent modloader (e.g. with AvoidWrappedLoader [very recommended if you do]), or you got confused by why a part of the Avoid addon loader behaves in some way, here's a few rules to know:

  1. Loader Presence
    Although Avoid currently runs on single modloaders, you should expect that it might provide interfaces into multiple.
    For example, you should not assert mod types; a NeoForge mod should be deemed possible next to a Fabric mod.

  2. Avoid addons should not be platform mods
    Avoid tries to skip loading of platform mods, as there's no way to skip loading of a platform mod.
    This is done because, if it wouldn't, the log would say the mod has been loaded "twice". Which would be weird.

    Yea, this is the real reason

Avoid Framework


    🏚️ 1. Home
    📽️ 2. Creating your mod
    🌄 3. Adding assets to your mod
    🧊 4. Creating a block
    💧 5. Creating a fluid
    ✏️ 6. Creating an item
    🎯 7. Creating an entity selector
    🤖 8. Creating a command
    ⌨️ 9. Creating a keybind
    🐺 10. Creating an entity
    🌫️ 11. Creating a fog
    🔩 12. Creating an item component
    🔮 13. Creating an effect
    📚 14. Language support & adding libraries
    🚩 15. Deprecation rules
    ⏳ 16. Loading philosophy


Migrations


    🧳 v1.25 -> v1.26
    🧳 v1.26 -> v1.27

Clone this wiki locally