Peek, whispered goosey-ganders for all!
There's now a sister-mod to Peek named Peek Alias, the relationship between Peek and Peek Alias is that the people who need to dispense information (likely a guild/raid or such) will have Peek enabled, and the leader will have Peek Alias. So the two mods bounce off each other well.
What's this? It sounds voyeuristic.
Oh it is, to a degree.
Peek allows you to send information about yourself at another's behest, and if they have Peek installed then you can get information about you. Peek acts as a server for dispensing any kind of information someone could require (almost), and it really is at its best when used in a guild.
Peek works by watching for its own codeword, and then an information request, then it dispenses the information requested.
For example, let's say your guild leader typed:
!peek xp restedxp money
You'd reply:
<Peek> XP: 49%
<Peek> Rested XP: 12%
<Peek> Money: 109g 80s 42c
Another situation could be in a raid, the leader might want to know who'd need the helm that Onyxia just dropped, the leader could:
!peek head
And you'd reply:
<Peek> Head: [Absolutely Dashing Toupée of the Aged Action-Star]
...or something like that.
Sounds interesting, tell me more!
Okay! Peek can also handle quest information, it can scan bags for item counts, it can check any and all equipped items, it can reply with combat rating information, and more's being added all the time! If you feel something needs to be peeked, let me know and I'll try and get it in.
What can it do right now?
I'm glad you asked! Here's the list ...
- list: Calls the following list in-game!
- amount-[item name] (andbank, optionally): Item count for item name.
- objectives-[Quest Name]: Printout of progress on objectives for that quest.
- reputation-[Faction Name]: Returns the faction reputation status.
- durability: Averaged durability across all equipped items as a per centage.
- maxhealth: Your maximum health as a number.
- maxpower: Your maximum mana/energy/rage as a number.
- health: Your current health as a per centage.
- mana: Your current mana/energy/rage as a per centage.
- crweapon: Weapon Skill (CR)
- crdefense: Defense Skill (CR)
- crdodge: Dodge (CR)
- crparry: Parry (CR)
- crblock: Block (CR)
- crmeleehit: Melee Hit (CR)
- crrangedhit: Ranged Hit (CR)
- crspellhit: Spell Hit (CR)
- crmeleecrit: Melee Critical (CR)
- crrangedcrit: Ranged Critical (CR)
- crspellcrit: Spell Critical (CR)
- crmeleetakenhit: Melee Hits Taken (CR)
- crrangedtakenhit: Ranged Hits Taken (CR)
- crspelltakenhit: Spell Hits Taken (CR)
- crmeleetakencrit: Melee Crits Taken (CR)
- crrangedtakencrit: Ranged Crits Taken (CR)
- crspelltakencrit: Spell Crits Taken (CR)
- crmeleehaste: Melee Haste (CR)
- crrangedhaste: Ranged Haste (CR)
- crspellhaste: Spell Haste (CR)
- crmainhand: Mainhand Weapon Skill (CR)
- croffhand: Offhand Weapon Skill (CR)
- crranged: Ranged Weapon Skill (CR)
- crexpertise: Expertise (CR)
- head: Helmet.
- neck: Necklace or other similar piece of armour.
- shoulders: Shoulder-pads, spaulders, et cetera...
- back: Cape.
- torso: Chest armour.
- shirt: Fancy non-armour shirt.
- tabard: Self-explanatory.
- wrists: Bracers.
- hands: Gloves, Gauntlets, et cetera.
- waist: Belt.
- legs: Leggings of all sorts.
- feet: Boots and shoes of all kinds.
- fingera: Ring on finger #1.
- fingerb: Ring on finger #2.
- trinketa: Trinket #1.
- trinketb: Trinket #2.
- mainhand: Main-hand held weapon.
- offhand: Off-hand held weapon/combat-item.
- ranged: Equipped gun/throwing.
- ammo: Type of ammo and amount.
- baga: Bag #1's bag type.
- bagb: Bag #2's bag type.
- bagc: Bag #3's bag type.
- bagd: Bag #4's bag type.
- xp: Current experience (per centage).
- restedxp: Rested experience (per centage).
- money: Print out of current amount of money.
This amount/objectives stuff, could you explain it more?
Ceratinly, let's cover amount first.
The syntax is: amount-[item name] (andbank, optionally)
- Amount is just the keyword to get the information.
- Item Name is the name of the item, you can type this (providing you apply the brackets) and you can use any case (all's good as long as the spelling's right). You can also supply an item link.
- Andbank basically implies that the bank should be counted too, you can supply the andbank operator if you wish the player's bank contents to be counted too.
Here's an example:
!peek amount-[mageroyal] andbank
This would return:
<Peek> Amount: 32
Next let's cover objectives...
The syntax is: objectives-[Quest Name]
- Objectives is just the keyword to get the information.
- Quest Name is the name of the quest, it can be typed but only if you add the brackets and type the quest in exact case (unlike amount, it can't be done in all lower-case due to restrictions in the quest API). The quest name can also be a link.
Here's an example:
!peek objectives-[Cleaning up Haus]
This would return:
<Peek> Objectives: Worried Bystanders: 1/10, Drunken Barflies: 4/10, Leery Barmaids: 2/5, Background Colour: 4/5, Rabid the Barkeep: 0/1, The Grogerator Mk XI: 0/1, Bobbin Threadbare: 0/1.
...or maybe not, but you get the idea.
Any other settings or fiddlywidgets I should be aware of?
A few.
If you don't want to see your own output from Peek (what you send after a Peek request), then you can delete the showoutput = true line in Peek.lua, that'll force Peek to suppress your own output text. So if that line is deleted and someone does '!peek xp', you won't see the '<Peek> XP: 32.19%' line.
If you want to block Peek from scanning a channel, there are a few lines at the top of Peek.lua you can delete, this is commented in the file so it's easy to understand. Just crack open Peek.lua in notepad and if, say, you wanted to stop it from parsing party chat, then delete the appropriate line.
Peek has a blacklist, too! Open up PeekIgnore.lua in a text editor and you'll see how that works, it's been fully commented with detailed instructions as to how it works. So if you want to stop folks from snooping around in your bags or the like... well, now you can! Now people can only peek what you let them peek.
I know I could add a GUI for these options, but that'd mean embedding libraries, using a GUI, having a SavedVariables database, and so on, and so on... and that'd be really taking away from the vision of what Peek is, wouldn't it? So I'm staying away from that. I accept that the users of Peek are going to be an intelligent niche of the community anyway to want to use a text-based transmission system instead of a GUI, so I don't think that this method of handling options/blacklisting would be hard for you ladies and gents at all.
So that's all, then?
Yup, that's what Peek does. It's designed to be an incredibly slim and lean transmission medium for information that friends/parties/raids/guilds would need in-game, but without any bloat or hidden channel-spam. Peek is what you see, nothing more, nothing less.
Any plans for the future?
I'd like to get in the ability to check whether players know certain recipes, but aside from that I'm pretty much almost done!