Grid raid mods world of warcraft addons gasco abu dhabi contact


The compact grid of unit frames lets you select a group member quickly, while keeping a good overview of the whole group. It shows as much information as possible without overloading you. It allows you to customize what information you see, and how you see it. It works in both party and raid groups, and supports pets and vehicles.

Want more features? The Grid core tries to include only features which are generally useful for all classes and roles, but makes it easy to add new features with a simple plugin API for developers. Over 75 third-party plugins are already available!

HINT: The WowAce interface for adding translations is quite cumbersome. To make the process easier, you can use the Export function on WowAce, copy the exported data into your text editor, fill in your translations, and then paste them back into WowAce using the Import function. Credits

Grid was originally conceived and written by Maia and Pastamancer in late 2006. Phanx has been the primary developer since late 2009. Jerry wrote the original pet support code. Mikk designed the icon. jlam added some advanced options for auras. Greltok has helped a lot with bugfixing. Finally, lots of people have contributed translations!

Anything beyond that? Maybe, but probably not. I haven’t had an active WoW subscription in over 2 years now, and haven’t done any serious raiding since Wrath, which was about 8 years ago. I took over Grid after its original author quit WoW at the end of Burning Crusade and nobody else was patching it. I’ve been hoping for years now that someone will show some interest in at least fixing some of the outstanding bugs, but apart from one person who helped out a bit in mid-Mists of Pandaria, that hasn’t happened.

While I’m still maintaining most of my addons at a basic level, Grid really needs more than "basic level" attention at this point, and it’s impossible to test changes without an active subscription (since the low level characters I can log into on an inactive account can’t join raid groups) so I’m pretty limited in what I can fix or change.

Right now, I don’t have BFA beta access, and don’t expect to get a beta invite since my account is inactive, so there won’t be a Grid update until the expansion pre-patch goes live (or the expansion itself, if there isn’t a pre-patch like there usually is). If you’re feeling adventurous, you can download untested BFA updates from GitHub ( but it’s likely that more updates will be needed that aren’t listed in the official "API changes in the expansion" thread.

If you have any programming experience, you can take a look through the list of outstanding issues and the source code and see what you can do. If you’re familiar with Git at all, opening a pull request on GitHub is preferred, but if you’re not, you can just provide a patch, or even a modified file.

It’s not. WoW is notoriously bad at correctly identifying the actual source of "taint", which is what happens when addon code touches something. Normally taint is fine (and it’s unavoidable since all addon code is automatically considere "tainted") but it becomes a problem when it spreads into "secure" parts of the default UI.

All that error means is that somewhere, at some time, Grid may have touched something, that touched something else, that touched something else, that 27 steps down the chain, met something that was touched in a bad way by another addon 8 steps back up a different chain, and then in 3 more steps there was an attempt (by someone, which could be Grid, the other addon, a third unrelated addon, or even the default UI code) to touch something in a "secure" code path that fails because of the earlier bad touch.

Grid shouldn’t really be tainting anything, since it creates all of its own frames and doesn’t modify any Blizzard frames, but it probably is if it’s getting blamed in an "action blocked" error. Unfortunately I can’t test this very effectively since I haven’t had an active account in about 2 years now and therefore can’t access any group content, let alone raids, but if you see this error fairly consistently, you can gather some helpful information by doing this:

4. Without logging out, find the "taint.log" file in your "World of Warcraft/Logs" folder. Upload it somewhere (it will be quite large, possibly several MB) and post a link to it here, along with the full text of the error message (not just the first line).