01-20-2013, 07:32 PM
Ok, it seems the current hooks are stable enough, so now it's time to go crazy about the new hooks. And since forum isn't really an efficient way of doing this kind of stuff, how about we use the bugtracker for this?
So I invite anyone having an idea for a hook to write it down in the bugtracker, possibly as a "feature request" task type and start the summary with "New hook: ..."; use one issue for one hook or one group of related hooks (for example, "inventory window hooks"); try to describe what the hooks should cover, when exactly they should fire, what parameters you'd recommend, what actions to take if the hook callback returns true (what kind of cleanup should MCServer do, if any at all), maybe some example usage, etc. The more information you provide, the more attractive it will be to us developers and thus more likely to get implemented soon
Thank you all in advance.
So I invite anyone having an idea for a hook to write it down in the bugtracker, possibly as a "feature request" task type and start the summary with "New hook: ..."; use one issue for one hook or one group of related hooks (for example, "inventory window hooks"); try to describe what the hooks should cover, when exactly they should fire, what parameters you'd recommend, what actions to take if the hook callback returns true (what kind of cleanup should MCServer do, if any at all), maybe some example usage, etc. The more information you provide, the more attractive it will be to us developers and thus more likely to get implemented soon
Thank you all in advance.