Solved Many small VS one big? =D

Discussion in 'Plugin Development' started by KittyKatt, Jan 29, 2013.

Thread Status:
Not open for further replies.
  1. Offline


    I'm just curious what would be best between developing many small plugins, example 1 for death messages, another that does mute, another that does jailing and so on etc, or just one BIG plugin that does everything?
  2. Offline


    one big would be much less resource intensive. Bukkit only has to load one plugin rather than a ton of them and the content would be largely redundant, i.e. registering listeners and onEnable etc in all plugins rather than once.
  3. Offline

    lDucks Retired Staff

    Heh, ladies like em big, heh.

  4. Offline


    For the vast majority of cases, multiple plugins would be better. Having one plugin to rule them all might seem like a good idea, but this is a somewhat naive view.

    First, you will likely never see a measurable difference in performance from breaking the plugins up. That and proper coding standards alone should be enough to convince you.

    That said, you will see a huge improvement in ease-of-maintenance in having multiple plugins, as they will be simpler to remove/update.

    Also, what happens when you upgrade or want to remove a function? If you have multiple plugins that have their dependencies properly configured, you can delete it without a second thought. However if you have one massive plugin, removing functionality could break it.

    Finally, troubleshooting when there are errors is vastly simplified if each plugin only does its own job.

    In the past for my own server I used to maintain one big plugin, however as it grew and for the reasons above I ended up breaking it into individual modular plugins, and I'm much happier with that solution.

    TL;DR: I've done both, and multiple is better.
    KittyKatt likes this.
  5. Offline


    Well then scratch my idea :3
  6. Offline


    It leaves the question if its better to reduce the load on bukkits event system or not.
    If you have a full plugin suite your plugins can directly interact with each other.
    So you could code your own event management system and get rid of lots of redundancy.
    Still the bukkit event handling seems to be pretty well implemented and if its performance is good i could skip coding that.
  7. Offline


    I'm not sure if you noticed, but this thread was last active Jan 29 2013. I'm sure the author has figured this out by now.
    jimuskin likes this.
  8. Offline


    Sorry, thought id rather search the forums and answer in an existing thread. Where else can i get infos?
    Start a new thread?
  9. Offline


    Well if the thread you're posting on is several months old, then yes.
  10. Offline

    1Rogue Retired Staff

    You should split plugins up like you would split anything else up: based on function, necessity, and purpose.
Thread Status:
Not open for further replies.

Share This Page