(187Kb)

Updated: 02-25-15 12:03 AM

Add Favorite

Install Help

Pictures

File Info

Compatibility:	The Adventure Continues (6.1)
Updated:	02-25-15 12:03 AM
Created:	06-06-09 05:00 PM
Downloads:	123,751
Favorites:	245
MD5:

FaceShooter

Version: 1.3.1

by: Crowfeather, Celetaras

FaceShooter is a shot recommendation addon for hunters.

Based on your resources like cooldowns and focus it tries to recommend which spell should be cast next.
It is a complete strip back to basics of the former version of FaceShooter, with the new and changed features developed from there.

1.3.1 - 25 Feb 2015
Simple version number change for 6.1

1.3.0 - 24 Feb 2015
Cooldown Sprial Returns!
Altered Black Arrow cooldown from 30sec to 24sec due to 6.1 changes
Coding for Barrage now properly handles the channeled spell
Still aware of issues regarding Explosive shot occasionally 'sticking' due to Lock and Load

1.2.9 - 14 Feb 2015
Faceshooter should now work when mounted on a Telaari Talbuk or a Frostwolf War Wolf

1.2.8 - 14 Feb 2015
Re-packaged zip file. No code change

1.2.8 - 11 Feb 2015
Serpent Sting is now explicitly checked for and Arcane Shot is suggested when it is about to fall off
Issue resolved when Cobra Shot still suggested occasionally when Focusing Shot talent is selected.
Horde should now be able to use Faceshooter while riding a Frostwolf War wolf. I don't have a Horde char so please test and let me know.
Survival focus dump now changed to Arcane Shot

Still an issue is the glitch where Explosive shot gets stuck. It's reproducible but still investigating the root cause.

1.2.7 - 14 Dec 2014
FaceShooter will correctly disable itself if not a Hunter or lower than level 90
Kill Shot now improved. You must however have one of the following on your Action Bars:
- The Kill Shot spell, ie dragged from the spell book to your Action Bars
- A Kill Shot macro with the exact Kill Shot icon
If neither of these are on your Action Bars, Kill Shot is disabled and not recommended by FaceShooter

1.2.6 - 30 Nov 2014
Fix for Kill Shot on BM spec (Incorrectly applied MM Draenor perk)
Focus Fire / Frenzy proc now recognized and suggested in shot recommendations
Faceshooter will work if riding a Telaari Tabuk
Focusing shot partially implemented but still under development and test - Use with caution

1.2.5 - 18 Nov 2014
Bug fix for focus calculation errors for SV and BM spec

1.2.4 - 16 Nov 2014
Added Dreanor Perks:
-Max focus increased by 20
-Kill Shot works on targets < 35% health
Known issues to be resolved:
-Does not recognise when Kill Shot resets its CD if the target does not die from it.
-Faceshooter does not check specifically for which Dreanor Perks are active, so only enables them when your level is 98 or greater.

1.2.3 - 7 Nov 2014
Bug fix for a specific situation which resulted in Aimed Shot never being recommended during Careful Aim phase

1.2.2 - 5 Nov 2014
- Careful Aim now implemented for Marksman, Prioritizes Steady and Aimed Shots when Target health > 80% or when Rapid Fire is active. Can be enabled / disabled / enabled for boss level targets
- Now accounts for lowered shot costs when Bestial Wrath is active
- Still to come: Steady Focus and Frenzy

1.2.1
- Fix for Barrage
- Barrage option now enable by default
- Now correctly identifies friendly units

1.2.0
-No changed code at all. Just repackaged as a zip not rar

1.2.0
- Removed: Hunters Mark, Lynx Rush, All T13 and T14 set bonuses, Lynx Rush & Serpent Sting (Now Passive), Aimed Shot breakpoints, Master Marksman etc.
-Amended/Updated: Lots...
Still under development:
- Careful aim not implemented yet
- Steady Focus not ready for release
- Frenzy / Focus fire mechanism not implemented yet
- No level 90+ features implemented yet (Dreanor perks, Focusing shot etc)
- Shot rotation still not as accurate as I'd like, seems to delay signature shot a bit too much, sometimes suggests Steady/Cobra shots a bit too much

Optional Files (2)

File Name	Version	Size	Author	Date	Type
Faceshooter fix for patch 5.4.1	5.4.3	133kB	Alkayder	02-14-14 01:21 AM	Addon
Faceshooter blink fix 5.3	5.3	15kB	dwil	05-25-13 10:49 PM	Patch

Comment Options

Page 17 of 30

« First

Last »

05-03-11, 12:06 AM
GlideRoggan A Kobold Labourer Forum posts: 1 File comments: 11 Uploads: 0	Cooldown circle I'm not sure it's related to the cooldown circle bug, but I haven't had the bug since I changed the line 1305 obj.btn.texture = obj.btn:CreateTexture(nil) to obj.btn.texture = obj.btn:CreateTexture(nil, "BACKGROUND") which is was in earlier releases.

05-03-11, 12:25 AM
Crowfeather A Fallenroot Satyr Forum posts: 28 File comments: 114 Uploads: 1	Ah thanks, I'll keep that in mind. Unfortunatly the bug is kind of difficult to reproduce. Sometimes it works perfectly fine for extended periods of time so verifying the fix is difficult.

05-04-11, 01:47 AM
tuff_ghost A Kobold Labourer Forum posts: 0 File comments: 14 Uploads: 0	Still broken 1. Delete Faceshooter addon directory and all Faceshooter-related files in WTF folder 2. Install Faceshooter 3. Load up WoW, attempt to disable or hide TTL frame ("hiding" it does nothing) 4. Attempt to resize spell icon frame #1 - single lua error every time 5. Relog, get spammed with endless TTL-related lua errors

05-05-11, 05:04 PM
thomhunt A Kobold Labourer Forum posts: 0 File comments: 7 Uploads: 0	First, I want to say I love this addon and thank you for taking the time to put it together! I have downloaded the recent update and after using it, I have had to go back to the 1.0.1a fan update version. Reason being, for the MM rotation it has the option to use aimed shot during hasted effects. The BM rotation also works much better. On the current update for BM, Arcane shot doesn't move showing its cool down. Also, it is suggesting shots that are either on cd or there is no focus for. I don't know if its possible to merge parts of the two, but if the MM shot rotation options as well as the BM rotation from the 1.0.1a fan update version were added to the current update it would be superb.

05-06-11, 01:50 AM
Crowfeather A Fallenroot Satyr Forum posts: 28 File comments: 114 Uploads: 1	Fixed the TTL module bugs - both hiding while still using the ttl data for HM/SpS and disableing the module completely shouldn't throw errors anymore Also specced to BM to check out tomhunts issues. I didn't seem to have any of those but maybe that's because of the fix suggested by GlideRoggan and the ttl fix were already incorporated in my version by then. Concerning Aimed Shot vs Chimera Shot when hasted - I'd rather use the haste value itself than checking for certain buffs. At the end of the day it doesn't really matter if my AimS is down to 1.5s casttime because of heroism/bloodlust, rapid fire or sinestra's haste buff (or any other effect really). So the real question is - at which point does AimS become better than CS?

05-06-11, 03:29 AM

GlideRoggan

A Kobold Labourer

Forum posts: 1

File comments: 11

Uploads: 0

Originally posted by Crowfeather
Fixed the TTL module bugs - both hiding while still using the ttl data for HM/SpS and disableing the module completely shouldn't throw errors anymore

Also specced to BM to check out tomhunts issues. I didn't seem to have any of those but maybe that's because of the fix suggested by GlideRoggan and the ttl fix were already incorporated in my version by then.

Concerning Aimed Shot vs Chimera Shot when hasted - I'd rather use the haste value itself than checking for certain buffs. At the end of the day it doesn't really matter if my AimS is down to 1.5s casttime because of heroism/bloodlust, rapid fire or sinestra's haste buff (or any other effect really). So the real question is - at which point does AimS become better than CS?

I combined the two.
First of, my AimS do more damage than CS, so when casttime is enough low I switch from arcane to AimS.
I mean, if I can cast AimS near GCD with more damage than CS and also without cooldown, I would.
In the fanUpdate there was a value "aimsSpeed" in the conditions for AimS which I included in your updated version. The fanupdate didn't look for certain buffs, but instead whenever it requested the resources, it looked at casttime for AimS.

Anyway, good to see you up and working

05-06-11, 04:03 AM

Crowfeather

A Fallenroot Satyr

Forum posts: 28

File comments: 114

Uploads: 1

Originally posted by GlideRoggan
I combined the two.
First of, my AimS do more damage than CS, so when casttime is enough low I switch from arcane to AimS.
I mean, if I can cast AimS near GCD with more damage than CS and also without cooldown, I would.
In the fanUpdate there was a value "aimsSpeed" in the conditions for AimS which I included in your updated version. The fanupdate didn't look for certain buffs, but instead whenever it requested the resources, it looked at casttime for AimS.

Anyway, good to see you up and working

Yeah, that's what I've been talking about. Instead of looking at the buffs, look at casttime (or rangedhaste which is basically the same).

In my current working version I implemented basically 4 different settings:

1. CA phase over haste breakpoint
2. CA phase below haste breakpoint
3. No CA phase over haste breakpoint and
4. No CA phase below haste breakpoint

You can define the haste breakpoint for both CA and non CA phase individually.

Default behavior is always hardcasting AimS while ignoring CS/SpS when in CA phase with more than 50% haste (-> less than 1.93s AimS casttime), casting CS on CD and use AimS as focusdump when either in CA phase but below 50% haste or not in CA phase but above 50% haste and last not least don't hardcast AimS at all when below 50% haste outside of CA phase.

I reasoned that 50% haste is the least you should get with ISS + rapid fire/heroism/bloodlust (assuming you've got at least 1% static haste) but you can always tweak it higher or lower if that better suits your gamestyle.

05-07-11, 01:19 AM

missdixy

A Kobold Labourer

Forum posts: 1

File comments: 2

Uploads: 0

Hello, I've Installed the latest versions and am getting a bunch of .lua errors in dungeons. I notice it usually happens when I start to aoe, although it happened a few times on single-targets as well.

Code:

Message: FaceShooter-1.0.4\FaceShooter_Functions.lua:811: attempt to compare nil with number
Time: 05/07/11 01:34:44
Count: 443
Stack: ...terface\AddOns\FaceShooter\FaceShooter_Functions.lua:1047: in function `PickSpell'
Interface\AddOns\FaceShooter\FaceShooter.lua:623: in function `Scheduler'
Interface\AddOns\FaceShooter\FaceShooter.lua:539: in function `OnUpdate'
Interface\AddOns\FaceShooter\FaceShooter.lua:513: in function <Interface\AddOns\FaceShooter\FaceShooter.lua:513>

Locals: self = <table> {
 es = 0
 debuffs = <table> {
 }
 CalcFocus = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:643
 haste = 1.1003786468506
 IsHMonTarget = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:778
 CheckCoS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:959
 spellStartedAt = <table> {
 }
 spellName = <table> {
 }
 CheckISS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:759
 GetDebuffs = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:462
 CheckSpS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:907
 tarHP = 0.44280810427152
 CheckRiF = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:768
 CheckES = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:792
 RegTilRdy = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:715
 GetResources = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:345
 now = 213030.67655617
 CheckAS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:933
 buffs = <table> {
 }
 lastCast = <table> {
 }
 Damping = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:701
 CheckBA = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:873
 Overcapped = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:725
 CalcTimers = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:564
 spellSentAt = <table> {
 }
 spell = "Steady Shot"
 SetResources = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:400
 focus = 39.830053308326
 CalcReg = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:693
 CheckET = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:886
 PurgeDebuffs = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:489
 CastSpell = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:498
 GetBuffs = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:439
 charges = <table> {
 }
 FocusGains = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:405
 CheckCS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:803
 recom = "Steady Shot"
 PickSpell = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:967
 IsNextToLastShot = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:750
 IsLastShot = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:741
 CheckKS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:899
 CheckKC = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:947
 spellEndedAt = <table> {
 }
 cooldowns = <table> {
 }
 NumCasts = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:427
 CheckAimS = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:839
 focusGains = <table> {
 }
}
btnName = "button1"
focus = 39.830053308326
spell = nil
FS = <table> {
 defaults = <table> {
 }
 CheckForDisabled = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:144
 modules = <table> {
 }
 IsInParty = <function> defined @Interface\AddOns\FaceShooter\FaceShooter_Functions.lua:208
 SetM

05-07-11, 02:52 AM
Crowfeather A Fallenroot Satyr Forum posts: 28 File comments: 114 Uploads: 1	That's a typo in the code - either replace all occurances of NoCaBreakpoint with noCaBreakpoint (the n has to be lowercase) in FaceShooter_Functions.lua or download v1.0.4b - Sorry for that.

05-07-11, 03:09 AM

missdixy

A Kobold Labourer

Forum posts: 1

File comments: 2

Uploads: 0

Originally posted by Crowfeather
That's a typo in the code - either replace all occurances of NoCaBreakpoint with noCaBreakpoint (the n has to be lowercase) in FaceShooter_Functions.lua or download v1.0.4b - Sorry for that.

Thanks a lot for the fast response, and for creating this awesome add-on!

05-07-11, 08:00 AM
UnlitPhoenix A Defias Bandit Forum posts: 2 File comments: 79 Uploads: 0	Hi! Brand new install giving some errors: Interface\AddOns\FaceShooter\modules\TimeToLife.lua:37: attempt to index field 'options' (a nil value) Interface\AddOns\FaceShooter\modules\TimeToLife.lua:125: attempt to index field 'db' (a nil value)

05-07-11, 11:22 AM
Crowfeather A Fallenroot Satyr Forum posts: 28 File comments: 114 Uploads: 1	1.0.4c fixed another stupid bug. While the new breakpoints option worked just fine preventing Aimed Shot from beeing hardcast Arcane Shot wasn't suggested either. @UnlitPhoenix Try deleting not only the faceshooter directory from your addons folder but also the faceshooter.lua from the savedvariables folder. Your bug is most likely due to an older version of the savedavariables. I'd suggest to delete the savedvariables for everyone who updates from an older version than 1.0.4 btw since quite a bit changed since then. Last edited by Crowfeather : 05-07-11 at 11:22 AM.

05-07-11, 01:17 PM

UnlitPhoenix

A Defias Bandit

Forum posts: 2

File comments: 79

Uploads: 0

Originally posted by Crowfeather
@UnlitPhoenix
Try deleting not only the faceshooter directory from your addons folder but also the faceshooter.lua from the savedvariables folder. Your bug is most likely due to an older version of the savedavariables.

I'd suggest to delete the savedvariables for everyone who updates from an older version than 1.0.4 btw since quite a bit changed since then.

I'd never installed this addon before, was the first time :O Earlier when I reloaded ui only one error came up. I'll try deleting the SV files when I get home tonight

Thanks!

EDIT: tried as you suggested and I keep getting those same two errors. Downloaded latest version too - both versions give exactly the same errors.

Last edited by UnlitPhoenix : 05-07-11 at 05:51 PM.

05-08-11, 12:44 AM
Crowfeather A Fallenroot Satyr Forum posts: 28 File comments: 114 Uploads: 1	I disabled all other addons besides FS, left no trace of the Savedvariables, I tried reloading the ui and changing the talent spec (MM/SV) but got no error. I'm sorry but I'm really at loss what might cause it for you. The error message indicates that there's no "options" field which should be created loading the FS main addon right after it verifies you're Hunter and level 80+. So either FaceShooter.lua loads after the TTL modules for some reason (can't reproduce), the option field is deleted somewhere along the way or FaceShooter doesn't create it at all even though it should very early on. Please try it with all other addons deactivated and see if it's a conflict with another addon.

05-08-11, 03:18 AM

UnlitPhoenix

A Defias Bandit

Forum posts: 2

File comments: 79

Uploads: 0

Originally posted by Crowfeather
I disabled all other addons besides FS, left no trace of the Savedvariables, I tried reloading the ui and changing the talent spec (MM/SV) but got no error. I'm sorry but I'm really at loss what might cause it for you.

The error message indicates that there's no "options" field which should be created loading the FS main addon right after it verifies you're Hunter and level 80+. So either FaceShooter.lua loads after the TTL modules for some reason (can't reproduce), the option field is deleted somewhere along the way or FaceShooter doesn't create it at all even though it should very early on. Please try it with all other addons deactivated and see if it's a conflict with another addon.

My hunter is level 77... that's why it isn't working? I didn't see a mention in the description of a level requirement

Page 17 of 30

« First

Last »

Report this File

Category Jump: