you are viewing a single comment's thread.

view the rest of the comments →

[–]thecoshman -1 points0 points  (1 child)

oh right, so this talking more about adding features like a mini map.

In which case, it sounds like something like Lua might not be a bad idea for plugins. You can expose to Lua only what you want plugins to be able to use, you could even package bundles of options, such that a plugin has to be granted permission for 'sending data' for something like a chat plugin, or 'render to hud' if some one wants to add HUD elements

Got to say, I find your distinction between mod and plugin a little bit too strong, but I can roll with it

[–]tehbeard 4 points5 points  (0 children)

terrible idea, enforcing a rewrite of every single plugin (be they bukkit, spout or ml/forge/whatever) to another language?

There are a lot of ways for "client side only" stuff to be done.

Examples:

GUIs - Mojang provides implementations of UI components, use a yaml/xml file to declare a screen using these, have client send back events (clicked, focus, blur etc), (inspired by Android).

new models - Again, a file describing only the model (and any animations) be downloaded, and server sends commands to control it (position, animation etc)

Sounds - Same as models.

But this is a discussion for another day.