I found a similer topic but it wasn't close enough to my idea to use that topic for discussion. My idea for being able to deliver client side mods to the clients that connect to a server is in short, make a "clientmods.jar" file on the client's computer in a folder named that of the server IP.
Server hosts will have to act as if they are modding their own minecraft.jar folder like anyone else would for stuff like modloader and such. Instead, they would do this in a blank jar file called "clientmods.jar" in the server's directory. In it they'll drag all the files nessicary like normal and run the server. When someone connects, this file will be transfered to either the minecraft.exe area ingo a sub folder or into %appdata%\.minecraft\bin\clientmods\0.0.0.0 (or) www.serverhost.com. The last bit of this being whatever you connect to on the server and this file being saved in it's location and read as if inside minecraft.jar but skipping META-INF from minecraft.jar. Dunno why that is even there if it's so useless. Anyway...
This would probably be hard to implement and make safe I know but this can only happen if the server is running so if it's a virus, the person running the server will also be infected. There should probably be more way of making sure but I assume this would be P2P so maybe have a popup warning when you try to load a modded server that says "Warning, this server is modded. The server wishes to download it's mods to your PC and you may be required to restart your game to load them. Be sure to scan the mod for viruses before you use it as well. We are not responsible for you using this server's mods and having something happen." (worded however you want) and a "Yes, download mod" and a "No, leave server" button below this.
nice idea, except i think the downloading mods thing could make the server slower
Only during a download. So maybe if you have like 50 new people per day and your server has a crap load of mods. Minecraft is already heavy on bandwidth.
Server hosts will have to act as if they are modding their own minecraft.jar folder like anyone else would for stuff like modloader and such. Instead, they would do this in a blank jar file called "clientmods.jar" in the server's directory. In it they'll drag all the files nessicary like normal and run the server. When someone connects, this file will be transfered to either the minecraft.exe area ingo a sub folder or into %appdata%\.minecraft\bin\clientmods\0.0.0.0 (or) www.serverhost.com. The last bit of this being whatever you connect to on the server and this file being saved in it's location and read as if inside minecraft.jar but skipping META-INF from minecraft.jar. Dunno why that is even there if it's so useless. Anyway...
This would probably be hard to implement and make safe I know but this can only happen if the server is running so if it's a virus, the person running the server will also be infected. There should probably be more way of making sure but I assume this would be P2P so maybe have a popup warning when you try to load a modded server that says "Warning, this server is modded. The server wishes to download it's mods to your PC and you may be required to restart your game to load them. Be sure to scan the mod for viruses before you use it as well. We are not responsible for you using this server's mods and having something happen." (worded however you want) and a "Yes, download mod" and a "No, leave server" button below this.
Only during a download. So maybe if you have like 50 new people per day and your server has a crap load of mods. Minecraft is already heavy on bandwidth.
Maybe, or those ops could just go get the plugin themselves if they want to make their own jobs easier.
http://forums.bukkit.org/threads/dev-spout-1-0-1-unleashing-the-flow-of-endless-possibilities-1000.29259/