W
weischbier
Guest
Stab to death - a Rogue CC
Closed
I stopped developing this CC
I stopped developing this CC
greetz
Weischbier
Last edited by a moderator:
Hi mate ... I cant seem to be able to set the cc to use combat .. somehow cant click on the combat option .. not sure if anybody else is having this problem.
Any ideas?
Thanks
Tekken
Oh, I'm so rolling a rogue now, will test out.
Please wait a few seconds while Honorbuddy initializes.
[BG]: Bloodthirsty Gladiator v. 1.3.1 loaded
Building spell book
Spell book built
Could not compile CC from C:\Users\xxxxxxxx\CustomClasses\Stab to death!
File: Stab to death.cs Line: 26 Error: The type 'StdCC.Rogue' already contains a definition for 'Name'
File: Stab to death.cs Line: 28 Error: The type 'StdCC.Rogue' already contains a definition for 'Class'
File: Stab to death.cs Line: 30 Error: The type 'StdCC.Rogue' already contains a definition for 'Me'
File: Stab to death.cs Line: 38 Error: Type 'StdCC.Rogue' already defines a member called 'slog' with the same parameter types
File: Stab to death.cs Line: 44 Error: The type 'StdCC.Rogue' already contains a definition for 'WantButton'
File: Stab to death.cs Line: 55 Error: The type 'StdCC.Rogue' already contains a definition for '_configForm'
File: Stab to death.cs Line: 56 Error: Type 'StdCC.Rogue' already defines a member called 'OnButtonPress' with the same parameter types
File: Stab to death.cs Line: 69 Error: The type 'StdCC.Rogue' already contains a definition for 'NeedHeal'
File: Stab to death.cs Line: 98 Error: Type 'StdCC.Rogue' already defines a member called 'Heal' with the same parameter types
File: Stab to death.cs Line: 128 Error: Type 'StdCC.Rogue' already defines a member called 'AutoAttack' with the same parameter types
File: Stab to death.cs Line: 139 Error: Type 'StdCC.Rogue' already defines a member called 'Combat' with the same parameter types
Disabling flight checks. - Paid Plugins or Lifetime User Detected
new Decorator(ret => !<YoursettingsPathhere>.MoveDisable && Me.GotTarget && !Me.IsFacing(Me.CurrentTarget),
new Action(ret => WoWMovement.Face())
),
also, include this in code if you want it to face:
Code:new Decorator(ret => !<YoursettingsPathhere>.MoveDisable && Me.GotTarget && !Me.IsFacing(Me.CurrentTarget), new Action(ret => WoWMovement.Face()) ),
Gibts was neues zu den Fehlern?
Some news about the loading issues?
gru?
skusku
Fixed!
I'm looking for someone with good knowledge of Combat playstyle.
No, my CC's will never support movement. But thanks for sharing!
greetz
Weischbier
Why not mate?
What? I tried using this PoS CC earlier, and the second a mob was LOS'd I died. cause i can't do SQUAT whilst not facing. and what do you mean by "wanna be able to control it 100% of the time?" You cant control shit whilst it's up? You can't move it(cause HB tries that) you cant fight(the CC does that) all you can do, is NOT afk so you have to be there, WATCHING EACH fight making sure it faces. Which makes the CC obsolete...
Before making harsh accusations, maybe you should read the instructions on the first post. This is meant to be used with the "Combat - No Movement" or "Lazyraider" bot, which don't move your character at all outside of combat. This is NOT meant for grinding or leveling. It is for users who want to control all the movement of their character (generally instances or raids) but do not want to have to worry about spamming their combat rotation, which is ALL this CC is meant to do.