Any arms pvp profiles?
The line is bold to highlight the fact that I thought the comment could be equally applied to your own post. In regards to your (I am assuming) sarcastic quip about my spelling, I am happy to inform you that I am not American and thus it is spelled correctly. Sarcasm doesn't translate well in the written form, a good way I have seen people make it clear is to add a cheeky /end sarcasm tag after their text. Your reply is quite childish and you are again merely belittling people instead of making constructive critism, it does not take a huge effort to phrase a criticism in a positive manner - check Ninjaderps post on the same topic if you would like to see someone expressing annoyance at leech postings whilst maintaining a constructive turn of phrase.I can't believe you couldn't understand my sarcasm from the first quote, and on the 2nd one, I have no idea why you made that line bold. It doesn't make any sense. Maybe you should "realise" that there is spell checking. That reminds me, here's a quick guide on how to use the spell checking (I'll put it in terms even you can understand):1. If you spell something incorrectly, there will be a red squiggly line underneath of the incorrectly spelled word, for example if you type "realising".
2. Rghti-click the word that has been misspelled, and select from the list that appears the correct spelling of the word.
3. ???
4. Profit.
PS: Mods: Please sticky this guide.
I use Pqr for some months.
Is it possible to get ban for this ?
u can get banned for everything thas not really legal in wow.......^^
but im using pqr now since 1.5years or something, and never having probs or getting banned or any shit.......and also dont read anything about that someones gotten banned for using pqr...^^
D3 Prices if i wna sell (EU)
![]()
I don't know if this affects PQR, since i'm not using this, but another private program.
IsSpellInRange seems to be bugged on some spells, this is what i have so far:
Living Bomb
Frost Strike
Distract
Envenom
Cobra Shot
Immolate
Incinerate
Impending Victory
Also a user on the US froms reported this: [Bug] Paladin: Fist of Justice vs. WoW API - Forums - World of Warcraft
I guessed that, but wonder if have something to do wth people getting execution errors with some addons or error comes from another source.![]()
Last edited by Pearl461; 09-06-2012 at 02:46 AM.
Try setting a global or local to get the spell info first like this
--BloodThirst
bloody = GetSpellInfo(23881)
then you can write out your check like this
if IsSpellInRange(bloody, "target") == 1 then
CastSpellByName(GetSpellInfo(118000),nil)
return true
end
It works for me when I do that, when I first tried it the way you are talking about LazyLazy it didnt work, I think its to do with using getspellinfo, but anyways, it should work for you the way i suggested.
Oh yea here is the api info: IsSpellInRange("spellName", [unit]) - Is nil for no valid target, 0 for out of range, 1 for in range.
Read more here: API IsSpellInRange - Wowpedia - Your wiki guide to the World of Warcraft
This takes into account talents etc. but watch out for the 'nil' return.
You will get a 'nil' if:
The spell cannot be cast on the unit. i.e. attempting to check range using 'Frostbolt' on a party member will always return 'nil', similarly testing 'Heal' against an enemy target will also return nil.
If the unit is not 'visible' (see API UnitIsVisible) then you will get a nil, and not a '0' as you might expect.
The unit doesnt exist (e.g. 'target' when you have nothing targetted)
The current player does not know this spell (so you cannot use 'Heal' to test 40 yard range for anyone other than a priest)
It can be used for scanning raid members distances, but just take care what spell you use. For example scanning heal range will start throwing out 'nil' if a raid member is mind controlled.
HOPE IT HELPS!!
Last edited by knightnova1; 09-06-2012 at 03:00 AM.
I'm guessing that was for my IsSpellInRange bugs.
So i'll make myself a bit more clear then
Even tho i use another program than PQR, it has nothing to do with this as i tested this with absolutely no addons installed (removed the entire addon directory), both 32bit and 64bit WOW tested and failed.
Since there is a use ability already coded be sure you change both 10's to 14, check carefully since there are two references to 10 you need to change in the ability.
Also be sure your on use trinket is in slot 2 else you would be wanting to change 10 to 13 in the above example.
Another way would be to add /use 14 in the action part of any given burst ability, such as zealotry or wings.
Oh and why would you have an agi trinket and not a str one?
Thanks for the response, i do know how IsSpellInRange works with 0, 1 nil returns.
The thing is, this worked prepatch.
Pre Patch
Doing IsSpellInRange("Living Bomb", "target") would return 1 when player was in range of target to cast Living Bomb
Post Patch
Doing IsSpellInRange("Living Bomb", "target") return nil no matter the scenario. In range, out of range, not a valid target or what ever you can come up with.
Just got some info from a fellow developer. He said it apparently bugs out for spells that comes from beeing a certain spec. So this makes me want to test abit more. Cause if thats the case (as mage). Then Nether Tempest, Living Bomb & Frost Bomb should behave all the same, returning a nil on IsSpellInRange.
So you, i still consider this a bug on Blizzards behalf and i'm only posting this for ppl to be aware of when doing range checks.
Last edited by Bgreen12; 09-06-2012 at 05:11 AM.