InventoryOnPar
This addon provides a scoring mechanism for your kit and others that you target. Allowing you to get a numerical value to compare your kit to others. This could be really useful on a raid to see the relative scores of members to work out who is best placed for a particular role etc.
You can see the score of others when you target them. It stores these scores in a table you can view with /iop show. You can view and set the options using /iop options. If you have Titan Bar or FuBar installed you can view your score and get access to the table and options forms by clicking on the Titan Bar or FuBar score.
It also shows a "paper doll" character sheet similar to your regular character sheet except the borders of the of your equiped inventory item icons are colour coded by comparing your current level with the ITEM Level (note NOT minimum level) of your equiped items. It also shows a colour coded Item Level indicator in various game tooltips. Plus if you use Titan you can see your overall on par "score" on your titan panel.
The idea is that you click a button on your character sheet or click on the Titan Panel or FuBar item and get instant feedback on what kit is out of date and ought to be replaced. The colour coding helps this as you can instantly see grey and green items as candidates for replacement. Note just because an item is grey or green doesn't mean that you must replace it. You may prefer your grey/green item's balance of stats to higher level items that are available. So do remember its a guide not an instruction :-)
The scale is the usual Grey/Green/Yellow/Orange/Red, as follows :
Grey - at least 5 lvls below yours (aka why are you wearing/using that rubbish)
Green - 2 to 4 lvls below yours (aka you should think about upgrading that bit of kit)
Yellow - one lvl below to one lvl above yours (aka suitable for your character level)
Orange - 2 to 4 lvls above yours (aka nice bit of kit you've got there)
Red - 5 or more lvls above yours (aka thats a bit special isn't it)
Also White - Item slot empty; and Blue - Item not recognised or not in item cache (marked as unsafe).
This idea has been extended to cover tooltips so hopefully all game tooltips should now show an items actual level colour coded according to how appropriate the items level is for your character. This works in auction houses, in quest rewards, trade and should work just the same in need/greed rolls too.
The "score" feature simply sums the difference in levels between your equiped items and your level. It gives a default score for uncommon (green) items and adds a bonus for rare items (blue), epic (purple), legendary (orange) or artifact items. The idea is to give an overall measure of how good your kit is. At very low levels your score will change rapidly as you get equipment but it should soon settle down. You should aim to always keep the number as high as possible, the higher it is the better equipped you are. Every time you level up your score will also change as the score is relative to how good the kit is for your level.
In version 2.20 a major new feature was added to log the Par score of other players that you encounter. It simply logs everyone you target within inspection range and within the level range you configure and stores their info, this includes not only their scores but the list of items they were wearing. You can view the log by typing
/iop show
on the command line or by right clicking on you Titan Bar or FuBar addin.
With the UI display form you can view the scores of players you have captured data of this shows their level, class, guild, date recorded and score. You can sort by any of these columns by clicking on the column title. When you left click on a players name it opens the Paper Doll character sheet and shows the players character sheet as it was when you captured it. This allows you to inspect someone at leisure simply by targeting them. You can view their kit days or weeks later although there is a protection mechanism to prevent a disconnect if you were to view items that the server hadn't seen since a reset.
It has been used extensively as a raiding equipment check tool by numerous guilds. The idea being the the scores give a guide as to how good someones kit is, and if their kit is not up to scratch they can see what needs upgrading. Various guilds adopt different minimum kit levels to raid a particular instance. For example a score of 250 is a common figure seen as a minimum score to raid Karazhan, and 400 to raid Gruul's Lair. This is not hard and fast scores but guide figures set by guild leaders. The idea being that a raid leader can leave out of a raid someone who's kit is just not up to scratch in favour of someone who is more likely to assist the raid. As such this is quite a useful and powerful tool for raid leaders.
In groups and in a raid there are two additional commands :
/iop raid
/iop party
These commands instantly scan everyone within inspect range in your raid or your party. Thus saving you having to manually click on each individual. The results are stored in your IOP table so you can view them at leisure later.
You can get the Titan panel module in the modules directory and the FuBar Module from http://wow.curse.com/downloads/wow-addons/details/fu-bar_iopfu.aspx
If you like this AddOn, please vote for it!
@persheal
Indeed I noted that myself will see if I can fix, however my focus at present is for v4.00 working by Tuesday for Patch 2.0. At present it is all working bar colour on tooltip, suspect this is a typing error.
So yes you will have a workinig version for patch day.
After inspecting someone's kit I look back at the list of results I got and looked back at what the person had.
His kit level showed my score, not his.
not a major bug, but simply a little esthetic issue.
Think I fixed it can you confirm - a nil value from a tooltip could return a nil value for item level this now should return a "not found" value.
I think it only means that your addon have to work with the current patch.. "Anyone caught uploading someone else's mods in order to get a Beta key will be banned from the site." would reinforce that. So you just have to upload the addon on their site and you should be good to go. Seems that blizz are trying to get every addon maker into tbc .. Doesn't hurt to try right ? :)
"I have written a couple of mods that I use personally but haven't uploaded to any site. One or two of them might be useful to other people; if I upload them now, am I eligible for the beta signup? I could really use a beta key to make sure my mods will work in the expansion."
Answer: "If you have a legitimate mod on the site and apply for it, you get a key. Period."
I got the error message when i shifted into druid catform and back with ItemRack enabled:
error: attempt to concatenate local `itemLevel' (a nil value) addon: InventoryOnPar file:InventoryOnPar.lua line:597
I'm using the german client version.
I just noticed the following from the BC API changes :
http://forums.worldofwarcraft.com/thread.html?topicId=36975623&sid=1&pageNo=1
Notice the following which is fantastic news :
UPDATED itemName, itemLink, itemRarity, itemLevel, itemMinLevel, itemType, itemSubType, itemStackCount, itemEquipLoc, invTexture = GetItemInfo(itemID|"itemLink") -- Now returns item level WARNING - This change is not backward compatible
ie: Finally they have added ItemLevel so I can recode the addon to remove any need for item tables, ie: every single item in Burning Crusade will work with IOP from the beginning. So from day one you will be able to compare your kit with others.
Now if only I could actually test this.
http://wow.allakhazam.com/news/sdetail8209.html?story=8209 It was a while ago so I don't know if it's still active..
Given the issues raised at http://forums.worldofwarcraft.com/thread.html?topicId=15401595&sid=1&pageNo=1 and http://forums.worldofwarcraft.com/thread.html?topicId=36975623&sid=1&pageNo=1 I am keen to test IOP on the beta BEFORE the patch goes live.
Blizzard have announced that the game will be in the shops from 16th January 2007. This suggests that the 2.0 patch will be implemented possibly with the US server reset the previous week 9th Jan or possibly on the 16th itself however the EU realms reset on a Wednesday so I am not sure how this will work.
I suspect that they will implement the patch at least a week if not 2 weeks before BC comes out. The patch will break a large number of addons (with lua 5.1 compliance) and render some for example: Decursive; CTRA(emergency monitor); Benecast; Needylist; completely inoperable (due to the new UI restrictions on targetting/conditional display etc during combat).
Whilst I do not think IOP will be seriously affected, other than needing a LARGE update of extra items, I would like to test it. I and others are also pressing for Blizzard to include ItemLevel as a return value from GetItemInfo() if they implemented this then IOP code size would shrink a lot as there would be no need for all the data tables.
Thus if anyone knows if I can register somewhere to get a beta test of the EU realm servers so that I might test this addon. Is there somewhere I can sign up as a addon developer to get on the test systems? I'd rather not wait until the public test realms become available as I imagine the queuing times for them will be painfully long.
I've added a new feature so that now on the tooltip it shows your average kit level as well as your character level. This is great for level 60s who can see that their kit is level x. My kit is level 65 at present with an IOP of 261.72.
At present I did some mucking about with the delete old records thing but not having a great deal of success the lua table handing code is nightmarish dealing with nils, empty slots or arrays closing up using .remove. Not entirely sure the best way to do the code. I'm sure there are tons of examples but I've just been too focused on adding to my now 5 pieces of Tier 1 kit. 8 MC Bosses down in our first 6 weekends raiding, with first 6 so easy we farm them and 96 items of Tier 1 kit dropped so far. A veritable deluge so soz guys but my focus has been on playing game rather than coding for it. I will get back to some coding stuff soon, as the speed through MC slows down (just Majordomo & Raggy to go).
My suggestions: 1. Lower the HeadSlot's minLevel variable down to 24 in localization.lua. 2. Make Trinket0Slot's minLevel variable 35 (leave Trinket1Slot's minLevel at 40) in localization.lua. 3. Add a checkbox in your options window to enable/disable a box labeled "This character is an engineer." which would change the head and trinket minLevel variables to their proper settings for a character who has engineering.
Yes you are right I did change the values upwards and included a bit of "slack" so that characters were not immediately penalised on hitting a new level but would have a few levels to get the item slot filled. I was rather pleased when after comparing all the item levels of the COMMON items that they worked out at 20,30,40. This seemed really sensible and looks as if it was part of blizzards design to work it out this way.
What you missed in your suggestions was the fact that if you have the slot filled BEFORE the min level you get a substantial IOP bonus score over others of that level.
Please be aware that the purpose of the addon is to give a reasonable guide as to your kit levels and indicate when replacements are needed. It also gives a guide as to how good your kit is vs someone else. This is useful in raiding and for instance my guild will be starting a policy of BWL requires an IOP of at least 150+ preferrably 200+ before members are accepted for sign up to an event. This gives us a guide as to whether or not someone's kit is up to the task.
To return to your individual suggestions.
1) I could understand perhaps 25 but why force mail users to wear a bit of cloth just to give a higher score on a addon designed to aid kit not force change. I just don't see that giving a big negative at 25 is the way to go. I'd rather give a big plus to those that go out of their way to get the extra kit, despite how silly it might look :-))
2) Ok so someone switches the trinket to slot 1 and gets a boost because it has a higher minimum??? NO this is just not workable.
3) Again if an engineer wants to make extra kit and GET A BONUS from having that fine. However I am not about to encumber the code with a lot of additional checks and balances just to suit a very limited set of circumstances.
So very sorry but I am rejecting your suggestions as I think you missed the basic point that if the slots are full BEFORE the minimum level you get a BONUS score over others. ie: I am now coding for bonuses not penalties.
Did you see my guild website reply? Basically answer is yes please, you can send me details to [email protected]
First off, let me thank you for a great addon that I use all the time on every one of my characters.
However, I used to have a issue with it that I had corrected manually by editing the localization.lua and modifying the required levels of slots. This mainly being the Trinket and Head slots. In the past, they had been set very low, which would have made sense if my character was an Engineer. Out of all the characters I have, only one is an Engineer, and so most of my time with low level characters is spent staring at a negative value for their equipment rating. To solve this, I went in and changed the values on my own system, and everything was perfect.
Now, with the release of the 3.6x version, this has been changed, yes. The values have been increased, and I'm glad. However, I don't think they were changed to the proper numbers. I almost feel as though you set them to their current values to give a little slack in when characters get a head armor and trinkets.
You currently have the head slot defined as a level 30 slot. If you're an engineer, you can get a head armor at level 10, which is what 3.5x and before always were set at. However, on every single one of my characters, no matter what their class, I have always bought the Azure Silk Hood at level 24 for them. Minimum level for head armor should be set at 24, though putting it at 30 only makes a difference when comparing your inventory to others (in my opinion, they, or you, should be penalized for not having at least a basic head item, even though the penalty should be on a sliding scale. ie: not having a head armor at level 60 should be more of a penalty than not having a head armor at level 50).
Trinkets - Any user can get ONE trinket at level 20 - but not many do. If you were to do Warsong Gulch battlegrounds, and get your reputation with the Silverwing Sentinels (the Warsong faction) up, then you can purchase a trinket called either Rune of perfection or Rune of Duty (dependent upon class) from the faction's quartermaster. Should the minimum slot be changed from it's current setting at level 40? I wouldn't say so - besides, you can only get one trinket at level 20 - you'd have to set both trinket slots to a different minimum level required! Engineers can fill both trinket slots (if they tried and wanted to) at level 10 by creating/buying and equipping a Gnomish Universal Remote and a Minor Recombobulator. Level 10 (I believe it was) was the previous setting - again allowing for engineering, but penalizing non-engineers. Normal players who are not engineers and who do not take part in Warsong Gulch enough to get the reputation required to purchase trinkets get their first trinket at level 35 (Cold Basilisk Eye), and their second trinket at level 40 (Ankh of Life). Both of these items are random drops, but the point is that you "could" have them, if you wanted them.
My suggestions: 1. Lower the HeadSlot's minLevel variable down to 24 in localization.lua. 2. Make Trinket0Slot's minLevel variable 35 (leave Trinket1Slot's minLevel at 40) in localization.lua. 3. Add a checkbox in your options window to enable/disable a box labeled "This character is an engineer." which would change the head and trinket minLevel variables to their proper settings for a character who has engineering.
The first two things would be simple to accomplish, and I have made (and will continue to) the change on my own installation of the addon. The third suggestion might take a bit of coding, but nothing extravagant. Anyhow, these are just a couple of ideas to toss around.
Again, thanks for a great utility!
I noticed that you added more strings to the localisation.lua Here is the deDe translation of these:
IOP_POOR = "Plunder"; IOP_COMMON = "Gew\195\182hnlich"; IOP_UNCOMMON = "Ungew\195\182hnlich"; IOP_RARE = "Selten"; IOP_EPIC = "Episch"; IOP_LEGENDARY = "Legend\195\164r"; IOP_ARTIFACT = "Artefakt"; IOP_UNKNOWN = "Unbekannt";
@Tronage - Ah yes the cleanup button - I'd forgotten about that soz. Will program that soon.
@Risingashes - my guild's website is http://www.anarchyalliance.com we are on the European Khadgar server. Latest news our first 4 weekends in MC and SEVEN bosses down, seems a bit too easy.
What was the link to your guilds website?
I seem to remember there being one here but either I can't see it or it was removed.
Any chance of getting this operational soon? I love inspecting others to get their IOP score (random people, my raid etc.) however my list can grow rather large, and I don't need to retain this information... Mostly just looking for the moment. So I'd like to be able to wipe the data. Also currently IOP takes 1.217 seconds to load on startup, and is taking 9.323 megs of ram because fo the database (stats provied by warmup addon). I'd like to be able to wipe the database, but only way to do that currently is to delete the saved variable file (outside fo game). Thanks for a great addon!!!
I had a look at fubar and yes it would appear to be simple enough to convert. However I have not seen a simple barebones Fubar module.
What I would like to do is take a Fubar module that does exactly what my titan one does eg: show a value on the bar, hover or left click to show a tooltip and right click to show a window.
If you can tell me where such a thing is I'd happily permit someone to write a conversion. However I have NO plans to start using FuBar myself. I am happy with Titan and can really see zero reason to change.
FuBar is very obviously written much more professionally, and as such demands strict compliance with its model. If someone can show me a module where the only change is the calls to the necessary IOP commands then hey presto you have FuBar support.
However at present I am far too focused on getting my Guild (I am the GM) through Molten Core. Three weekends in MC so far 6 bosses down. I can see no reason to rip and replace Titan bar and thus I personally won't be investing the time in working out FuBar support. I am however convinced that similar to Titan support its a trival operation for someone who has the time.
Wish I had discovered this mod sooner when dealing with guild raids. Fabulous idea. But...most cool kids have moved on from Titan and are now using FuBar (http://www.wowinterface.com/downloads/info4571-FuBar_2.0.html).
Most/all Titan mods are also available for FuBar now. FuBar has several unique mods that you can't get on Titan. More devs are working on FuBar mods than Titan ones currently. And so on.
Yes, Titan is still the most downloaded here on Curse, but that means nothing because FuBar isn't available here.
Also, the APIs for FuBar are very clear and well described; its very easy to port things over (http://wiki.wowace.com/index.php/FuBarPlugin-2.0).
For sure, keep Titan support for those that still use it. But for those users who have moved on to FuBar, would be really nice to see support implemented in this.
(am just a user who would like to be able to have this show up in FuBar)
V4 seems to be working perfectly fine. Thanks ;)