Skip to content
This repository has been archived by the owner on May 26, 2018. It is now read-only.

FAQ

Jump to bottom
cpw edited this page Apr 18, 2012 · 15 revisions

Specific FAQs

Some frequently asked questions about FML

  1. Are you serious? FML?
    Yes, FML is a deliberate acronym. I know what it means. It also means Forge Mod Loader. The original longer name was FMLMP. I shortened it slightly because FMLMP does mean what you think.

  2. Is this compatible with MLMP?
    No. This is a clean re-implementation of ModLoader capabilities on the minecraft server. It had become necessary for something to replace the rather confused tangle that was MLMP- delays, old/broken API, bugs in MLMP meant a better solution was called for. FML is that solution. Compatibility was primarily targeted at ModLoader, a defacto published standard on the client side. MLMP introduced several unnecessary elements, especially Packet230, which with the "official" Packet250 became obsolete. Also, MLMP is an unpublished standard, meaning I could not usefully create a "clean" reimplementation.

    However I welcome pull requests aimed at reintroducing MLMP support into FML. It is my belief that such changes would be fairly small for FML to make. I will not add them myself, but this is a standing invitation for SDK or other acknowledged author of MLMP to submit pull requests against this open source library for that purpose.

  3. If you used ModLoader on the client as a reference, why aren't you completely compatible with it?
    There are several reasons:

    • Some API makes no sense on the server vs the client. The graphical code doesn't even exist so it can't work on the server.
    • Being a packet server is a different thing from being a packet client. You need to handle packets from the client to the server differently from server to client. So the API changes reflect that.
    • There's no such thing as the "MinecraftClient" on the server, so onTick has been simplified since it's unneeded anyway in general.

  4. Are you planning a client version?
    No. Not at present. Risugami is maintaining ModLoader satisfactorily. I don't wish to handle the extra graphical work required for a client implementation.

  5. Why do you have so much more code than ModLoader?
    This project is architected to be easy to inject into several environments- including the client and bukkit servers. By trying to separate the main "Loading" piece from the actual job of interacting with Minecraft, I hope I can make it easy to port the thin minecraft facades without significant effort.

  6. Do you have any how-to guides for using this at all?
    There is at least one on the minecraft forums written by AtomicStryker and others here. I will try and keep the list up to date.

  7. What's all the FMLModContainer and @Mod stuff about?
    That is an in-development re-imagining of how you would tell the system about your mod- based much more on meta-information rather than just on subclassing BaseMod and waiting for callbacks. Currently it's not really fleshed out at all.

  8. I have a mod X that does Y on ModLoader or ModLoaderMP but doesn't on FML.
    File an issue here please. Any discrepancies between MLMP or ML and FML need to be noted and fixed. Test cases or log files will help a lot. Thanks!

Clone this wiki locally