Does MultiboardReleaseItem() get rid of the handle?

This one basically says it all in the title. When you use MultiboardReleaseItem() does it do the same as, say, DestroyTrigger()?

Yes, it does, in the sense that it does not "destroy" the item causing your multiboard to crash or anything, it just releases it so it can be cleaned out later. Atleast that's the concept I imagined for it. I actually had yet to test this, but I think if you use MultiboardGetItem, you always get the same handle/item if you ask for the same item in the MB. So the overall leak is perhaps pretty limited to the item-count on the MB.

But anyways, When I noticed this function, I noticed also that the BJ functions used these functions, so I made my own versions of these functions that de-referenced the handle, made it zero-based (-1 for "complete row/col"), and made it's algorithm much more eficient for when it's used at a specific item (as by default it loops through the complete MB each time), so in my version it then directly goes to the requested row/col if it's not -1.

If you're interested in my functions, I can post them here (or in Chobo's PasteScript or The Vault)

~Cubasis

I can confirm that MultiboardGetItem, is kind of GetUnitLoc , creates a multiboarditem pointer , and you have to release it or it leaks, (unless you save it in an array like i do)

This is not quite what I had in mind for my question (you guys already answered my first one). Do multiboard items run from a base 0? Or it is 1? The native GetMultiboardItem(), does it run on base 0 or 1 for rows and colums? I am having some difficulty with my multiboard and that might be the problem.

GetMultiboardItem (Native functions) run zero-based ... the Blizzard.j functions work 1-based. That's why I made that change to the BJ functions, so they would also be zero-based.

in every situation, from item slots to multiboard items, all natives use 0 based, and blizzard.j functions are worthless anyways