What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Warlock CC] skiWarlock 3.0 for HB2 - ALL TREES -

Status
Not open for further replies.
I have a level 14 lock. Just sitting I have not played him in a long time. What talent tree should I use?

Unfortunately this isn't really a CC question but to answer it from my own perspective I Googled "warlock leveling spec 3.3.3" and after some reading I opted for Affliction which seems to have done well so far. The spec I'm working toward is:

http://www.wowhead.com/talent#IfxMbzMAoVA0IktZE0RV
 
I have a level 14 lock. Just sitting I have not played him in a long time. What talent tree should I use?

Why are there 2 threads with the same name under warlock?
[Warlock CC] skiWarlock 3.0 for HB2 - ALL TREES -
and 2.0

something that we should maybe know?

3.0 is a major rewrite, 2.0 is no longer used (hence locked).
 
There should be special mode for fighting gray mobs way below our level - no pet, no dots, only dd of choice and/or wand.
 
New version up, tons of changes, I'm about to pass out, will field questions tomorrow.
 
Testing the new version i noticed that it says

Chose ski's Warlock v3.$Rev$ as your CC!


instead of a cool version numbre:(
and it doesnt tell me what specc im using still uses the correct autodetect is this intendet? anyway got about 30k xp/h more than with the old one(may be a lil cause im 3 lvls higher than when i tested it last) but still looks smoother and faster

Oh maybe you could add a proper spelllock and dispell mechanic for the felhound if this is possible(like dispell the warlock ) and only spelllock when the target is actually casting
 
Testing the new version i noticed that it says

Chose ski's Warlock v3.$Rev$ as your CC!


instead of a cool version numbre:(
and it doesnt tell me what specc im using still uses the correct autodetect is this intendet? anyway got about 30k xp/h more than with the old one(may be a lil cause im 3 lvls higher than when i tested it last) but still looks smoother and faster

Oh maybe you could add a proper spelllock and dispell mechanic for the felhound if this is possible(like dispell the warlock ) and only spelllock when the target is actually casting

The $rev$ is a tag from the svn to update the version number automatically, I just didn't check it out in the proper fashion. You can safely ignore that.

For the spec part, is it initializing the wrong spec? There should be a log entry that says "Initializing: xxxxxxxxx", where X is one of the three trees that has the most points in it.

For the felhunter, I thought their logic was improved so that it would dispel/silence correctly as opposed to all the time, but correct me if I'm wrong.
 
Id like to know what's the difference between this version and the one before ?
 
Id like to know what's the difference between this version and the one before ?

Code:
45: - CreateAddList(): Pet will now attack mobs attacking the caster first. List returned is now sorted by - IsAttackingCaster -> Pet->Mob Distance -> Caster->Mob Distance
- combatAdds(): Pet will only Attack mobs that are attacking the caster - this should kill the original target faster or try to pull the mob of the caster - this is not perfect yet
- moveWithinRangeToPet() + moveWithinRangeToMob(): Added checks to determine if Mob is alive, pet died, etc - this should help fix the "Move" bug where the caster would get stuck on "Move" until the mob died
- moveWithinRangeToPet() + moveWithinRangeToMob(): Fixed endless running bug
- moveWithinRangeToPet() + moveWithinRangeToMob(): Added IsMoving check with Stop() action to the end of each function
- Combat(): Mass Pull: Will moveWithinRangeToPet() every 2nd mob
- Combat(): Mass Pull: Code cleanup
- WoWPoint petPoint: Now checks Me.GotAlivePet not Me.GotTarget
- needRest(): Added petPresenceTimer check to Soul Link - this will stop the recasting of Soul Link on dismount
- Added PetAttack() - Makes the pet attack your CurrentTarget, also sets the red X charm on Pet.CurrentTarget - isnt perfect, does toggle icon on and off if ran on the same target more than once
- Combat(): Added !Me.Pet.GotTarget check to the default pet attack - If the Pet already has a target, dont change targets - Hopefully will result in less Pet target changing randomness
- combatAdds(): Change FaceStop() to Stop(); Face(); 

44:  - Combat(): Commented Find Target code
- Combat(): Find Target: Changed move code to moveWithinRangeToMob("Find Target")
- Combat(): Find Target: Fixed pet attack, was attacking if the mob was not alive
- Combat(): Find Target: Moved pet attack code above move code 

41:  - Combat(): Mass Pull: Does not reverse mobList after sort any more 


40: - Added moveWithinRangeToMob(sring logPrefix): Moves closer to mob for attacking
- Combat(): Mass Pull: Changed mobsList for{} loop to while{}, while now iterates until there are no more Objects in mobsList
- Combat(): Mass Pull: Fixed Pet->Mob distance sorting mid Mass Pull, mobsList is sorted by Pet->Mob distance then reversed - this will make the pet attack the further mob first during a mass pull (i.e. mobs attacking the caster)
- moveWithinRangeToMob() and moveWithinRangeToPet() logic updated - movement is much better
- HealthFunnel(): Me.Pet.HealthPetcent displayed after a funnel has finished
- CreateAddList() and CreateMobList() commented
- CreateAddList(): Add warnings updated - no more spam, more consistent, more information
- OrderKillList() renamed to SortKillList() - this method is still TODO
- CreateMobList(): Increased Pet->Mob from PullDistance to PullDistance * 1.5 

39:  - Initialize(): Changed returns
- Initialize(): Added automatic disable of fightAdds depending on known spells
- combatAdds(): Added Sleep of 1s after combatAdds() - this with the fightAdds override should help with the re-dotting issue
- combatAdds(): Removed HP Percent check of currenttarget
- Combat(): Mass Pull: Disabled resorting of mobsList as this was not working 100% - need to fix 

38: - waitWhileCasting() added after various spell casts in their respective Functions
- Added waitWhileCasting() below the single target rotation
 
Causes crashes:

Could not compile CC from C:\pirom\HB\CustomClasses\skiWarlock3.0-pre1921.cs!
File: skiWarlock3.0-pre1921.cs Line: 575 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 575 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 581 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 581 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 737 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 737 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 746 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
File: skiWarlock3.0-pre1921.cs Line: 746 Error: "Styx.WoWInternals.WoWObjects.WoWItem" enth?lt keine Definition f?r "ItemEnchant", und es konnte keine Erweiterungsmethode "ItemEnchant" gefunden werden, die ein erstes Argument vom Typ "Styx.WoWInternals.WoWObjects.WoWItem" akzeptiert (Fehlt eine Using-Direktive oder ein Assemblyverweis?).
 
Sometimes my guy likes to cast the first spell, and sit there and get beat on for like 5-10 seconds. Not sure why this is happening. Also my guy isnt Soulstoning himself either.
 
After watching bot for a good while, it does pretty good. Just not creating soulstones, sometimes lags to cast, and doesnt turn on Blood Pact with imp.
 
In PVP - don't fight :(

Code:
[09:14:39:546] Stop and dismount...
[09:14:40:425] Activity: Combat
[09:14:40:595]  Das Objekt des Typs "Styx.WoWInternals.WoWObjects.WoWUnit" kann nicht in Typ "Styx.WoWInternals.WoWObjects.WoWPlayer" umgewandelt werden. - From: Honorbuddy   bei TreeSharp.Composite.Tick(Object context)
   bei Styx.Logic.BehaviorTree.TreeRoot.Tick()SmartExceptionsCore.UnhandledException @ 988, offset:0

Can you give me a quick translation of that? I think it is something wrong with the HB api about wowplayer, but I'm not sure.
 
Sometimes my guy likes to cast the first spell, and sit there and get beat on for like 5-10 seconds. Not sure why this is happening. Also my guy isnt Soulstoning himself either.
Does this occur after a "[skiWarlock] FUNCTIONNAME: Move: DISTNACE yard from: MOBNAME" ??

Not sure about the soulstone, it works for me... make sure useSoulstone = true....

In PVP - don't fight :(
This hasent been tested in PVP.... use at your own risk
 
I'm having 2 different problem with healt Funnel
First, when pet go below 40% he start doing healt funnel and then he immidiatly stop after 1 tick when pet healt go over 40%
The settings are standard i didn't touched them se it should start healing the pet at 40% and stop at 90% (i'm demonology) instead he start just below 40% and stop at 40%.
The second problem is if pet go out of LoS to do a mass pull and his healt go below 40% the bot never realize that per is out of los or mob are out of los couse he try to heal pet, healt funnel doesn't work and bot keep spamming it withoud doing anything else till the pet die.
Log attached
Apart from that, this CC got better and better every day that pass than you :)
 

Attachments

Status
Not open for further replies.
Back
Top