Tips for Writing Mods - Page 2

Tanoh · 10/11/06, 8:02 AM

Originally Posted by Elethiomel

Not only wouldn't the code do what you'd think, it wouldn't work as it's not valid lua.

Oh yeah, sorry forgot about the then/end crap.

Originally Posted by Elethiomel

Also, to nitpick a bit, semicolons at the end of a line is optional in lua, and parenthesis in if statements are optional as well, so:

Stylistic and easier to read (imo).

Originally Posted by Andorien

Good coding practice, even in c/c++, is either [...]

Depends where you come from. I'm working as a perl programmer, for me there is no boolean type. :)

Kenco · 10/11/06, 8:33 AM

On the subject of variable naming, i find it is very convenient to define all your variables inside tables, basically like

mymod =
{
time = 20,
count = 1,
attack = function()
count = count + 1
end,
}

In this way it's possible to fit your entire mod into one variable. This has the added advantage of giving more convenient names to your variables.

Rogar · 10/11/06, 8:45 AM

Originally Posted by Kalman

Beyond that, coding a new mod for BigWigs is pretty simple if you look at a couple old ones; most of the research time in writing a new mod is figuring out what to trigger from and the intervals.

Regardless of the framework you're using, if you're writing boss timer mods then Transcriptor (another Ace addon) is really useful for post-fight analysis.