HeyRunes API design

Discussion in 'Plugin Development' started by chrisinajar, Feb 10, 2011.

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

    chrisinajar

    Finally got a server working with Bukkit, and my users are screaming at me for HeyRunes... I've put a lot of thought and done some proof of concepts and the new version should be a hellofalot more flexible and _freaking awesome_

    So here's my new concept for the API on HeyRunes... You create a class inheriting from the HeyRune object... There are a bunch of functions you can implemenet, including "int[][] runeShape()", "onActivate""onCreate", "onDestroy"... onActivate is called when the rune is "activated" via whatever method you told it to, including when it's clicked on, lit on fire, right clicked on, or walked on. Also, you will be able to specify which x,y coord is the activation point (no longer limited to just the center)... the onCreate and onDestroy will fire when the user completes the rune (places the last block) and when the user destroys the rune (removes any block)... The new rune checking algorythm should be faster and more generic too, and be much better for 3d runes at a future date.

    What do you guys think? Particularly those of you who made HeyRunes plugins for hMod...

    I'll write a much more detailed description of the API when I'm not at work...
     
Thread Status:
Not open for further replies.

Share This Page