World of Warcraft addon for detecting, managing, and tracking hostile players.
Currently entering beta phase. Please be detailed in all bug reports.
Features
- Detect enemy players (Horde or Alliance) in your area and see a list of the most recent activity.
- Indicate if enemies are engaged in PvP, what they are casting, and who they are targeting.
- Track kills of, and deaths by, enemy players and guilds.
- Keep notes on enemy players and guilds.
- Mark enemy players and guilds as KOS (Kill On Sight) and get alerted when they are detected.
- Turn on Tracking for an enemy player and get alerted when they are detected by another Stalker addon user.
- Send enemy position alerts to most channels (Say, Yell, Guild, Party, Raid, or Whisper)
Modules
- Stalker Monitor - Shows the most recent enemy player activity. Player information is on the left, and spell and target information is on the right. Players in this window will fade out over a short period of time if there is no activity from them.
- Stalker Viewer - Shows a history of all enemy player and guild encounters. It contains player information, kills, deaths, and your own notes. Player without kills, deaths or notes will automatically be removed after 24 hours.
- Stalker Alerts - Fully configurable alerts that tell you when enemy players, KOS players/guilds, and Tracked players are detected.
- Stalker Agent - When you are Tracking players the Agent communicates with other Stalker addon users and alerts you if someone detects the the player.
How it works
Stalker works by monitoring your combatlog. When it hears someone close by it attempts to guess their level and class based on the spell that they cast. So if it hears someone cast a Rank 5 Siphon Life, it identifies them as a Level 63+ Warlock. Note the + after the 63. This indicates they may be higher, but we only know they are at least this level. Once you target or mouse over the player Stalker will be able to determine definitively their level and the + will be removed.
What Stalker DOESNT do
- Doesn't give you special abilities. All its doing is monitoring your combatlog and making that data more accessible. There will be times where you see an enemy right in front of you, but if you don't target or mouse over them, or they are not casting anything, Stalker wont know about them.
- Doesn't tell you precisely where players are. The map coordinates that it generates for enemy players are YOUR position when you detected them, not theirs. There is no accurate way of determining their position. But since the range of the combatlog outdoors is 100yds, you know they are close if its alerting you about them.
- Doesn't work in Battlegrounds or Arenas. It's designed for world PvP.
------------------------------------------------------------------------
r25 | croy9000 | 2009-01-05 04:35:13 +0000 (Mon, 05 Jan 2009) | 1 line
Changed paths:
A /tags/0.5.24beta (from /trunk:24)
Tagging 0.5.24beta
------------------------------------------------------------------------
r24 | croy9000 | 2009-01-05 04:33:02 +0000 (Mon, 05 Jan 2009) | 2 lines
Changed paths:
M /trunk/Stalker.lua
Fixed bug with KOS Guild introduced in last commit.
Fixed bug where GetZonePVPInfo() was not reporting that player was in a sanctuary immediately after login. Added a initialized flag to delay combatlog and player targeting 5 seconds.
------------------------------------------------------------------------
r22 | croy9000 | 2009-01-05 03:11:34 +0000 (Mon, 05 Jan 2009) | 1 line
Changed paths:
M /trunk/Stalker.lua
Fix bug with nil being reported for new KOS Guilds.
------------------------------------------------------------------------
r20 | croy9000 | 2009-01-05 02:22:32 +0000 (Mon, 05 Jan 2009) | 2 lines
Changed paths:
M /trunk/Locales/Stalker-enUS.lua
M /trunk/Stalker.lua
M /trunk/StalkerConfig.lua
Fixed grammer errors in config panel (ticket 1)
Fixed bug with adding new KOS Guilds. Was removing whitespace characters. (ticket 2)
------------------------------------------------------------------------
r18 | croy9000 | 2009-01-04 05:01:21 +0000 (Sun, 04 Jan 2009) | 1 line
Changed paths:
M /trunk/StalkerAgent.lua
Fixed a bug where Agent chat channel was being joined to soon which caused it take the /1 slot. Added a 5 second delay.
------------------------------------------------------------------------
r16 | croy9000 | 2009-01-03 15:46:57 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/Stalker.lua
M /trunk/Stalker.toc
Updated version
------------------------------------------------------------------------
r15 | croy9000 | 2009-01-03 15:37:37 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk
Fixed externals path
------------------------------------------------------------------------
r14 | croy9000 | 2009-01-03 15:36:17 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk
Fixed externals path
------------------------------------------------------------------------
r13 | croy9000 | 2009-01-03 15:35:06 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
D /trunk/Libs
Cleaning up file structure
------------------------------------------------------------------------
r12 | croy9000 | 2009-01-03 15:27:38 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
Removing duplicate lib CallbackHandler
------------------------------------------------------------------------
r11 | croy9000 | 2009-01-03 15:22:38 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
Pointing to wrong Ace3 path
------------------------------------------------------------------------
r10 | croy9000 | 2009-01-03 15:17:21 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk
M /trunk/.pkgmeta
M /trunk/Stalker.lua
Packing changes
------------------------------------------------------------------------
r8 | croy9000 | 2009-01-03 14:06:01 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/Stalker.lua
M /trunk/Stalker.toc
Altered revision scheme
------------------------------------------------------------------------
r7 | croy9000 | 2009-01-03 13:57:52 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/Stalker.lua
More revision keyword fun
------------------------------------------------------------------------
r6 | croy9000 | 2009-01-03 05:31:48 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/Stalker.lua
Fixed revision issue
------------------------------------------------------------------------
r5 | croy9000 | 2009-01-03 05:27:28 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
A /trunk/Images/Flash.tga
Adding missing flasher image.
------------------------------------------------------------------------
r4 | croy9000 | 2009-01-03 04:57:13 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
Fixed path issue with LibDBIcon embed.
------------------------------------------------------------------------
r3 | croy9000 | 2009-01-03 04:44:58 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
M /trunk/Stalker.lua
Added Revision SVN property
------------------------------------------------------------------------
r2 | croy9000 | 2009-01-03 04:25:02 +0000 (Sat, 03 Jan 2009) | 1 line
Changed paths:
A /trunk/.pkgmeta
A /trunk/Fonts
A /trunk/Fonts/ABF.ttf
A /trunk/Images
A /trunk/Images/Bar.tga
A /trunk/Images/BarTimer.tga
A /trunk/Images/FlagKos.tga
A /trunk/Images/FlagPvp.tga
A /trunk/Images/FlagTrack.tga
A /trunk/Images/Pause.tga
A /trunk/Images/Play.tga
A /trunk/Images/Stalker.tga
A /trunk/Libs
A /trunk/Locales
A /trunk/Locales/Stalker-enUS.lua
A /trunk/Stalker.lua
A /trunk/Stalker.toc
A /trunk/Stalker.xml
A /trunk/StalkerAgent.lua
A /trunk/StalkerAlerts.lua
A /trunk/StalkerConfig.lua
A /trunk/StalkerData.lua
A /trunk/StalkerMonitor.lua
A /trunk/StalkerMonitor.xml
A /trunk/StalkerSpells.lua
A /trunk/StalkerViewer.lua
A /trunk/StalkerViewer.xml
A /trunk/embeds.xml
Initial commit
------------------------------------------------------------------------
r1 | root | 2009-01-02 22:19:08 +0000 (Fri, 02 Jan 2009) | 1 line
Changed paths:
A /branches
A /tags
A /trunk
"stalker/mainline: Initial Import"
------------------------------------------------------------------------
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP has a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
