Ok, so I was just thinking about this when I thought, "Hey, I'll just post this on suggestions."
Anyways, I heard Notch was adding "Modding Support" as in making it not illegal, and easier for developers to make mods by giving source code.
He said he wasn't going to implement an official modding API, so I was thinking he could do something like this:
1) Change handling of mods. Have it handled like a hierarchy. Minecraft vanilla content would be in mojang.vanilla. vanilla blocks would be in something like mojang.vanilla.blocks. The world generator would be in mojang.vanilla.generator. Specialized code, like the stuff that makes cave noises would be in mojang.vanilla.special. Stuff would also have different priorities, like 1 would be base priority. A mod with the 1 priority in a section overrides the default content. For example, phoenix terrain mod would be in rtb.phoenixterrainmod.generator. the priority for the generator in that mod would be set to 1, as it replaces the default world generator. However, a mod that would add ruins placed randomly would have a priority of 2, which means it adds onto the existing content.
2) A modloader type thing. Have hooks and stuff for block creation, texture loading, terrain generation hooks, etc. Also add hooks for multiplayer things, like deaths, chat, etc.
3) Mod installation/handling. Have a "Mods" or "Addons" folder in the .minecraft folder. You would place mods in there. Mods would be activated/deactivated via the texture/mod menu.
4) SMP mod support. When joining a mod enabled server, it would have a list of required mods, and a list of optional mods. It would ask you one-by-one to install individual mods, although it would not install any mods you already have, and you could choose not to install any optional mods. Like a mod that adds new blocks would be required, but one that plays music when you die is optional. When you install server mods, they would be installed to "minecraft/mods/servermods/[server name]/" Server mods by default will only be activated while on that server, however, if you like a mod, you can choose to install it for personal use. Oh, and you also can only use mods the server specifies, so you can't use flymod on a server that doesn't have it in their approved mods.
Please give me some feedback here. Constructive criticism is welcome, although flaming and trolling is not.
Anyways, I heard Notch was adding "Modding Support" as in making it not illegal, and easier for developers to make mods by giving source code.
He said he wasn't going to implement an official modding API, so I was thinking he could do something like this:
1) Change handling of mods. Have it handled like a hierarchy. Minecraft vanilla content would be in mojang.vanilla. vanilla blocks would be in something like mojang.vanilla.blocks. The world generator would be in mojang.vanilla.generator. Specialized code, like the stuff that makes cave noises would be in mojang.vanilla.special. Stuff would also have different priorities, like 1 would be base priority. A mod with the 1 priority in a section overrides the default content. For example, phoenix terrain mod would be in rtb.phoenixterrainmod.generator. the priority for the generator in that mod would be set to 1, as it replaces the default world generator. However, a mod that would add ruins placed randomly would have a priority of 2, which means it adds onto the existing content.
2) A modloader type thing. Have hooks and stuff for block creation, texture loading, terrain generation hooks, etc. Also add hooks for multiplayer things, like deaths, chat, etc.
3) Mod installation/handling. Have a "Mods" or "Addons" folder in the .minecraft folder. You would place mods in there. Mods would be activated/deactivated via the texture/mod menu.
4) SMP mod support. When joining a mod enabled server, it would have a list of required mods, and a list of optional mods. It would ask you one-by-one to install individual mods, although it would not install any mods you already have, and you could choose not to install any optional mods. Like a mod that adds new blocks would be required, but one that plays music when you die is optional. When you install server mods, they would be installed to "minecraft/mods/servermods/[server name]/" Server mods by default will only be activated while on that server, however, if you like a mod, you can choose to install it for personal use. Oh, and you also can only use mods the server specifies, so you can't use flymod on a server that doesn't have it in their approved mods.
Please give me some feedback here. Constructive criticism is welcome, although flaming and trolling is not.
Thank you. :smile.gif:
This is my first well received suggestion.
and also, your idea is good