Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Ah ok désolé. C'est bon maintenant. Merci encore l'ami. Tu dev encore le bot ou il est a l'abandon ? Et si je te payes tu pourrais m'aider a créer une routine de groupe complète avec un donjon d'exemple ?
  3. Yesterday
  4. Hello, your problem should sovled
  5. Hey @Droidz Can you unlock the use my licence with legion version 26972 ? Thanks.
  6. Last week
  7. Version 1.0.205

    4 downloads

    ⚠️ BETA WARNING ⚠️ This is a BETA version of the fight class. While extensively tested, it may contain bugs or unexpected behavior. CRITICAL REQUIREMENT: You MUST have a backup healing addon installed and ready to use manually. Recommended addons: HealBot Vuhdo Grid + Clique Elvui Keep your backup healing addon active and be prepared to take over manual healing if the fight class malfunctions or in critical situations. This is automation assistance, not a replacement for player awareness. Overview Advanced Restoration Shaman fight class featuring predictive damage analysis, anti-overheal mechanics, emergency totem protection, and intelligent drinking detection. Built with multi-threaded architecture for optimal CPU performance. Version: 12.1 Game Version: WotLK 3.3.5a Bot: WRobot Class: Shaman (Restoration spec only) Key Features 🔮 Predictive Healing System Damage Pattern Analysis - Tracks incoming damage and predicts future damage patterns (AoE, Spike, Steady) Anti-Overheal Engine - Calculates actual heal need by accounting for incoming heals, HoTs, and Earth Shield Smart Spell Selection - Chooses optimal heal based on efficiency scoring and predicted damage Emergency Detection - Predicts potential deaths before they happen 💧 Intelligent Drinking System (NEW!) Automatic Detection - Detects Drink/Food buffs on player Activity Pause - Stops all totem placement, buffs, interrupts, and dispels while drinking Emergency Override - Continues critical healing (<30% HP) using only instant spells: Nature's Swiftness combo Riptide instant heal Zero Mana Waste - Ensures full mana regeneration during drinking 🗿 Emergency Totem Protection Protected Emergency Totems - Mana Tide, Earth Elemental, Grounding, Stoneclaw cannot be overwritten by normal totems Smart Placement - Only places totems after 2+ seconds stationary Automatic Recall - Recalls totems when out of range (except emergency totems) ⚡ Performance Optimization Multi-threaded Architecture - Separate threads for healing (20ms), totems (250ms), utility (2000ms) Multi-tier Cache System - L1/L2 cache reduces Lua calls by ~30% Batch Operations - Checks multiple party members in single Lua call Thread-safe Design - All operations properly locked and synchronized 🎯 Priority Healing Nature's Swiftness - Auto-cast for predicted deaths (<15% HP after incoming damage) Tidal Force - Emergency crit healing for <25% HP situations Chain Heal - Optimal targeting for AoE damage situations (3+ injured) Tank Priority - Increased healing priority for identified tanks 🛡️ Automatic Utilities Wind Shear Interrupts - Priority list (heals > CC > damage spells) Cure Toxins - Automatic dispel of Poison/Disease when safe Water Shield - Maintains buff at all times Earth Shield - Monitors charges on tank, refreshes at ≤2 charges Earthliving Weapon - Automatic enchant application Mana Management Thresholds The fight class adapts behavior based on mana percentage: Mana % Behavior < 20% Emergency only - Mana Tide Totem, critical heals only 20-30% Conservative - Basic water totems, essential healing 30-35% Water + utility totems, moderate healing 35-85% Full earth totems, optimal healing rotation 85%+ All totems including air buffs (Windfury/Wrath of Air) Installation Download the .cs file Place in: WRobot/FightClass/ Launch WRobot Select the fight class from the dropdown menu IMPORTANT: Configure your backup healing addon (HealBot/Vuhdo/etc.) Requirements Mandatory WRobot (latest version) Restoration spec Shaman Backup healing addon installed and configured Recommended: 2000+ spell power for optimal performance Recommended Addons Omen - Threat monitoring DBM/BigWigs - Boss mechanics awareness HealBot/Vuhdo - Manual healing backup (REQUIRED) Configuration No configuration needed - the fight class adapts automatically based on: Party composition (melee vs caster ratio for air totems) Combat situation (damage patterns, health levels) Mana available (threshold-based behavior) Drinking status (activity pause/resume) Totem Durations Water Totems: Healing Stream: 300s (5 min) Mana Spring: 300s (5 min) Mana Tide: 12s (emergency) Cleansing: 300s (5 min) Earth Totems: Stoneskin: 120s (2 min) Strength of Earth: 300s (5 min) Earth Elemental: 120s (2 min, emergency) Tremor: 300s (5 min) Air Totems: Windfury: 300s (5 min) Wrath of Air: 300s (5 min) Grounding: 15s (emergency) Expected Performance Improvements Based on testing: 10-20% reduction in overhealing 15-25% mana efficiency improvement 20-30% CPU usage reduction 100% emergency totem protection Faster response time in critical situations Zero mana waste during drinking Known Limitations Beta Status - May contain undiscovered bugs Party Size - Optimized for 5-man content No Raid Frames - Works with default party frames and WRobot's detection Manual Intervention Required - Complex boss mechanics may need manual control Spec Specific - Restoration spec only, will not work with other specs Troubleshooting Fight class not healing: Verify Restoration spec is active Check WRobot product is started Ensure you're not mounted Verify party members are within 40 yards Too much overhealing: System is learning - give it 5-10 minutes Check spell power (needs 2000+ for accurate predictions) Totems not placing: Stand still for 2+ seconds Check mana threshold (needs 30%+ for most totems) Verify spells are learned Drinking detection not working: Ensure you're using standard food/drink items Check for conflicting addons that modify buff detection Support & Feedback This is a community project in beta testing. Please report: Bugs and errors Performance issues Suggestions for improvement Successful dungeon/raid completions Remember: Always have manual healing ready as backup. This bot assists you, it does not replace your awareness and decision-making. Credits Advanced anti-overheal prediction system Emergency totem protection logic Multi-threaded performance optimization Drinking-aware activity management Use at your own risk. Bot responsibly.
  8. Version 1.0.54

    3 downloads

    Restoration Shaman Fight Class v8.1 FINAL - BETA Documentation ⚠️ CRITICAL DISCLAIMERS BETA STATUS This fight class is in BETA testing phase. While functional, it may contain bugs or unexpected behavior. DO NOT rely on this as your only healing solution. MANDATORY BACKUP REQUIREMENT You MUST have a manual healing system running simultaneously: HealBot (recommended) VuhDo Grid + Clique Manual keybinds The bot can fail, disconnect, or behave unexpectedly. Your party/raid depends on you having a backup. CODE MODIFICATION WARNING This system contains intentionally designed race conditions between threads to simulate human-like reaction delays and imperfect decision-making. The threading model creates non-deterministic behavior patterns that mimic human healers. ⚠️ MODIFYING THE CODE CAN BREAK THE HEURISTICS: Thread timing adjustments may cause deadlocks or over-aggressive behavior Changing priority systems can make healing completely non-functional The multi-threaded architecture is fragile by design Test ALL changes extensively in solo content first If you modify anything, you're on your own. The threading system is tuned to create realistic human-like behavior patterns. Expected Log Behavior Thread Errors Are Normal You will see occasional errors in the WRobot log such as: [HEAL THREAD] Error: ... [TOTEM THREAD] Error: ... [UTILITY THREAD] Error: ... These errors are expected and can be ignored in most cases. The multi-threaded architecture intentionally operates with race conditions that occasionally produce logged errors. This is part of the design to simulate human reaction variance. When to Worry About Errors Normal: 1-5 errors per minute scattered across threads Acceptable: Brief error spikes during loading screens or zone transitions Problem: Continuous error spam (10+ per second) that doesn't stop Critical: Fight class stops functioning (no healing, no totems) If errors spam continuously for more than 30 seconds, restart WRobot. Otherwise, ignore them and watch your in-game healing performance instead. What To Monitor Instead of watching the log, monitor: Are party members being healed? Are totems being placed when stationary? Is mana management working? Are emergency abilities firing when needed? If yes to all = ignore the log errors. Overview This is a sophisticated multi-threaded Restoration Shaman fight class for WRobot (WotLK 3.3.5a). It features intelligent movement detection, smart totem management, predictive healing, and automatic interrupt/dispel systems. Key Features 🔄 Multi-Threading Architecture Healing Thread: 20ms tick rate (Highest priority) Totem Thread: 250ms tick rate (Normal priority) Utility Thread: 2000ms tick rate (Below normal priority) Race conditions between threads create 50-200ms variance in reaction times, simulating human behavior. 🚶 Smart Movement System Tracks player movement every 200ms 2 second stationary requirement before placing normal totems Emergency totems work while moving (Stoneclaw, Earthbind, Earth Elemental, Mana Tide, Grounding) Automatic Totemic Recall when moving away from totems 🗿 Intelligent Totem Management Normal Totems (Require Stationary): Water: Healing Stream (high damage) / Mana Spring (low mana) Earth: Stoneskin (high damage) / Strength of Earth (default) Fire: Smart selection based on mana and enemy count Air: Wrath of Air (default) / Resistance totems (boss-specific) Emergency Totems (Work While Moving): Stoneclaw: Healer under attack + <60% HP Earthbind: 3+ enemies near healer Earth Elemental: Party average <30% HP, 3+ enemies Mana Tide: <30% mana (3 min cooldown) Grounding: Enemy casting any spell within 30 yards (20s cooldown) Fire Totem Logic: <70% mana: Flametongue only (buff, no mana cost) 70%+ mana: Searing Totem (attacks) No enemies: Flametongue for buff Auto-reposition: After 5 seconds out of range 💧 Advanced Healing System Emergency Response: Nature's Swiftness: Instant cast at <18% HP Tidal Force: Critical heals at <25% HP Emergency threshold: <35% HP Smart Spell Selection: Riptide: Always first, instant HoT Chain Heal: 2+ targets below threshold Healing Wave: Critical situations, tanks Lesser Healing Wave: Quick response, moderate damage Predictive Healing: Tracks incoming damage patterns Pre-applies Riptide to targets about to take damage Anticipates group-wide damage 🛡️ Utility Features Auto-interrupt: Wind Shear on priority casts (heals, CC, high damage) Auto-dispel: Cure Toxins on poison/disease Buff maintenance: Water Shield, Earth Shield on tank Weapon enchant: Earthliving Weapon Grounding Totem: Automatically cast when any enemy begins casting Mana Management The system has four mana thresholds: Mana % Behavior <30% CRITICAL: Mana Tide Totem emergency, Mana Spring priority 30-50% Mana Spring priority, conservative healing 50-70% Mana Spring priority, Flametongue only (no attack totems) 70%+ Full offensive totem setup allowed Installation Download the .cs file Place in WRobot/FightClass/ directory Launch WRobot Select "Resto_Shaman_v8_Final" from fight class dropdown Configure your backup healing addon (HealBot, etc.) Start botting Ignore thread errors in the log (see section above) Configuration No external configuration needed. All logic is automatic: Movement detection: Automatic Totem placement: Automatic based on combat situation Healing priorities: Dynamic based on party health/damage Mana management: Automatic threshold-based Boss-Specific Features Auto-detects dungeons and adjusts totems: Loken (Halls of Lightning): Nature Resistance Totem Garfrost (Pit of Saron): Frost Resistance Totem Generic heroics: Standard totem setup Performance Monitoring The system logs status every 2 minutes: Healing pulse rate (target: 45-55 pulses/sec) Current mana percentage Group DPS (damage taken) Average party health Movement status Combat statistics Check logs for "PERFORMANCE" entries. Troubleshooting Seeing Thread Errors in Log Symptom: [HEAL THREAD] Error: messages appearing Cause: Normal race conditions in multi-threaded design Solution: Ignore them. Only worry if they spam non-stop or healing stops working. Totems Not Placing Symptom: No totems being cast Cause: Movement detection thinks you're still moving Solution: Stand completely still for 3+ seconds. Check logs for "MOVEMENT" entries. Over-aggressive Grounding Totem Symptom: Grounding every 20 seconds Cause: Working as intended - blocks any enemy cast Solution: This is normal behavior. Grounding has 20s cooldown built in. Low Healing Rate Symptom: <45 pulses/second in logs Cause: High latency or CPU bottleneck Solution: Close other programs, reduce WRobot settings, check your FPS/latency Totems Recalled Immediately Symptom: Places totems then recalls right away Cause: Bot thinks you're moving away from them Solution: Disable auto-follow, reduce movement speed during combat Not Using Mana Tide Symptom: Running OOM, no Mana Tide cast Cause: 3 minute cooldown restriction Solution: Working as intended. Mana Tide only every 3 minutes. Healing Stopped Completely Symptom: No heals being cast, party dying Cause: Critical thread failure or API disconnect Solution: Stop and restart WRobot immediately. This is why you need HealBot backup. Known Issues Thread errors in log: Intentional race conditions create occasional logged errors (see above section) Occasional totem spam: When rapidly starting/stopping movement Tank detection heuristics: May misidentify tank in unusual group compositions Fire totem repositioning: May be aggressive in high-movement fights Grounding cooldown: Will not fire more than once per 20 seconds even if multiple enemies casting Technical Details Thread Safety All shared data protected by locks Cached data expires after 300-1000ms Lua calls wrapped in try-catch blocks Spell cooldown tracking prevents spam Performance Optimization Party/enemy data cached to reduce API calls Buff/debuff checks cached 300-500ms Movement checks throttled to 200ms intervals Dungeon detection cached 30 seconds Spell Priority System Priority 0: Grounding Totem (enemy casting within 30yd) Priority 1: Nature's Swiftness (<18% HP emergency) Priority 2: Emergency healing (<35% HP) Priority 3: Totemic Recall (totems out of range) Priority 4: Emergency totems (danger situations) Priority 5: Normal healing rotation Priority 6: Normal totem placement (stationary only) Priority 7: Utility (buffs, dispels, interrupts) FAQ Q: Should I worry about errors in the log? A: No. Thread errors are expected. Only worry if healing stops working or errors spam continuously. Q: Can I change healing thresholds? A: Yes, but TEST THOROUGHLY. Modify GetCriticalThreshold(), GetPriorityThreshold(), etc. in EnhancedHealingEngine. Changing thresholds may break the heuristics. Q: Can I disable Grounding auto-cast? A: Comment out the HandleGroundingTotem() call in SmartTotemManager.PulseTotems(). Q: Why won't it place totems while moving? A: By design. Only emergency totems work while moving. Stand still 2+ seconds for normal totems. Q: Can I adjust the stationary timer? A: Change STATIONARY_TIME_FOR_TOTEMS in MovementTracker class. Default: 2.0 seconds. May break totem placement behavior. Q: Does this work in raids? A: Designed for 5-man dungeons. May work in raids but untested. Healing logic caps at 5 party members. Q: Why is my FPS dropping? A: Three threads running constantly. Reduce tick rates or disable utility thread if needed. Q: Is it normal for Grounding to cast constantly? A: It casts whenever enemies cast spells, limited by 20s cooldown. This is intended behavior. Q: The fight class stopped working completely, what do I do? A: Stop WRobot, restart it, reload the fight class. Use your backup healing addon until bot is stable. If it keeps happening, disable the fight class and heal manually. Safety Reminders Always have HealBot or similar running - This is not optional Watch your party's health bars - Don't blindly trust the bot Ignore thread errors in log - They're cosmetic unless healing stops Test in normal dungeons first - Don't jump straight into heroics Stay at keyboard - AFKing with a healing bot gets you reported Manual intervention required - Some mechanics need human response Credits This fight class uses intentionally designed race conditions and heuristic systems to simulate human healing patterns. The architecture is complex and fragile - modifications require understanding of multi-threaded programming and WRobot API behavior. Use at your own risk. Always have manual backup healing ready. Thread errors in the log are a feature, not a bug. They simulate human imperfection.
  9. Earlier
  10. if work whitch profile have any update showcase ?
  11. Hello, Direct access (simple but not ideal) : // You can reset the counter to 0 directly wManager.Wow.Helpers.StuckResolver.StuckCount = 0; Differential approach : // At the beginning of your recovery step, save the current value int initialStuckCount = wManager.Wow.Helpers.StuckResolver.StuckCount; // ... your recovery logic ... // After recovery, calculate how many new stuck events occurred int newStuckEvents = wManager.Wow.Helpers.StuckResolver.StuckCount - initialStuckCount; // Reset the counter to what it was initially plus any new events wManager.Wow.Helpers.StuckResolver.StuckCount = initialStuckCount; Local counter with events : var localStuckCounter = 0; wManager.Events.MovementEvents.OnPulseStuckResolver += cancelable => { localStuckCounter++; // cancelable.Cancel(); // if you want to cancel the automatic unstuck }; // Use localStuckCounter instead of StuckResolver.StuckCount // Reset localStuckCounter = 0 after your recovery
  12. Bonjour, Avez-vous ajouté le PNJ entraîneur (type WarriorTrainer ou autre selon votre classe) dans votre profil ou dans votre "NPC DB" (onglet "Tools").
  13. Такое только после релога, либо ты делаешь что-то не так
  14. Bonjour, Je ne sais pas pourquoi, mes personnage ne vont pas automatiquement learn leur spell quand il passent leur level et qu'ils vont en ville ou même si il y en a un juste à coté d'eu. Pourtant j'ai bien cocher les cases dans l'advanced setting.
  15. Hello, I think it's a case sensitivity issue. You need to enter the name exactly as it appears in-game. You also have many WoW addons installed, which can sometimes cause problems.
  16. the mount switches several times 21 сен 2025 10H43.log.html
  17. на 3.3.5 садится на маут спрыгивает, еще пару раз и двигается дальше 100% палево как исправить?
  18. Version 1.0.30

    7 downloads

    Advanced Blood Death Knight Tank - WRobot Fight Class Overview This is an advanced fight class for World of Warcraft 3.3.5 (Wrath of the Lich King) designed specifically for Blood Death Knight tanking. The class features sophisticated threat management, intelligent positioning, emergency cooldown usage, and automated combat mechanics. Key Features Combat System Optimized Rotation: Prioritizes high-threat abilities like Heart Strike, Death Strike, and Blood Boil Rune Management: Intelligent rune usage with emergency Blood Tap and Empower Rune Weapon Disease Management: Automatic application and spreading of Blood Plague and Frost Fever AoE Threat: Death and Decay positioning and Blood Boil for multi-target encounters Defensive Capabilities Emergency Healing: Death Strike, Death Pact, Rune Tap with health-based priorities Lichborne Combo: Uses Lichborne + Death Coil for self-healing and fear immunity Cooldown Management: Vampiric Blood, Icebound Fortitude, Anti-Magic Shell automation Fear Immunity: Advanced fear detection with Lichborne counter-measures Movement & Positioning Smart Positioning: Maintains optimal distance (1.5-4.5 yards) from enemies Line of Sight: Advanced pathfinding with obstacle detection and avoidance Stuck Detection: Automatic unstuck procedures with jump and strafe mechanics Manual Override: Detects manual player control and disables automation Threat Management Auto-Targeting: Intelligent target selection based on threat level and priority Taunt System: Dark Command and Death Grip for threat recovery Party Protection: Prioritizes enemies attacking party members, especially healers Installation Place the .cs file in your WRobot FightClass folder Load the fight class in WRobot Ensure you're in Frost Presence for optimal tanking Configuration Constants (Modifiable) private const float IDEAL_DISTANCE = 3.0f; // Preferred combat distance private const float MIN_DISTANCE = 1.5f; // Minimum distance before backing up private const float MAX_DISTANCE = 4.5f; // Maximum engagement distance private const float MAX_DISTANCE_FROM_START = 30f; // Leash range Timer Settings Threat Check: 250ms intervals Buff Check: 8 second intervals Emergency Check: 800ms intervals Auto Target: 400ms intervals Movement Update: 50ms intervals Ability Priority System Emergency Priorities (Critical Health < 35%) Death Pact - Sacrifices minion for instant heal Icebound Fortitude - 20% damage reduction Vampiric Blood - Increases healing received Death Strike - Healing based on damage taken Threat Generation Priorities Rune Strike - Highest threat per Runic Power (20 RP) Heart Strike - Primary single-target threat Death and Decay - AoE situations (3+ enemies) Blood Boil - Spreading diseases and AoE threat Defensive Priorities Lichborne + Death Coil - Self-healing combo (< 50% HP) Anti-Magic Shell - Against casting enemies Bone Shield - Maintained constantly Mark of Blood - Healing through combat (< 70% HP) Advanced Features Fear Handling Detects incoming fear effects from enemy casts Uses Lichborne for complete immunity to fear, charm, and sleep effects Falls back to Icebound Fortitude for damage reduction Self-heals with Death Coil while Lichborne is active Pathfinding System Line of Sight Detection: Uses TraceLine for collision detection Obstacle Avoidance: Calculates alternative paths around barriers Jump Mechanics: Automatic jumping over small obstacles Strafe Movement: Side-stepping around medium obstacles Combat Resurrection Raise Ally: Automatically resurrects fallen party members in combat Prioritizes close-range targets within interaction distance Maintains current target after resurrection attempt Auto-Looting Loots nearby corpses automatically after combat Maintains cache to avoid repeated loot attempts Respects combat state and manual control Manual Control Integration The system detects when you're manually controlling your character through: Keyboard input detection (WASD, QE keys) Movement state analysis Automatic disabling of all automated movement when manual control detected Troubleshooting Common Issues Character not moving: Check if manual control detection is working Not targeting enemies: Verify auto-targeting timer settings Spell failures: Ensure proper rune availability Positioning problems: Check MAX_DISTANCE constants Debug Features Extensive logging for all major actions Combat state tracking variables Timer-based activity monitoring Error handling with detailed exception logging Performance Considerations Object caching system reduces API calls Timer-based execution prevents excessive computation Synchronized movement state prevents conflicts Efficient enemy filtering and distance calculations Compatibility WoW Version: 3.3.5 (Wrath of the Lich King) WRobot: Compatible with standard WRobot APIs Specialization: Blood Death Knight (Tank) Group Play: Full party/raid support with healer protection Support Notes This fight class is designed for experienced users who understand Death Knight mechanics. The code includes advanced features that may require fine-tuning based on your specific gameplay needs and server configurations. For optimal performance, ensure your Death Knight has learned all major tanking abilities and maintain appropriate gear levels for your content.
  19. That's awesome! It's been a while since I've used Wrobot, I don't think they had this webpage when I was using it. Thank you!
  20. https://wrobot.eu/byme/CompatibilityReporting/index.php
  21. detected atm
  22. Good Afternoon, How safe is it to bot on Turtle WoW? I'm trying to find more clear answers on methods of how it should be done botting on their server. I've read they have good detection. I usually stay attended to the bot, just working on another screen while it's going. I've learned in the glider and HB days, it's not usually a good idea to leave it unattended. Allan
  23. Bot used for 10 minutes to try gathering in Outland and got banned the next day. I dont recommend using the bot on Warmane any more. Something seems to be detected
  24. This also has happened to me, and i believe its also something to do with their detection and Wrobot Movement as i got frozen by a GM being told that something im using is spaming their anticheat warden and to turn it off. No Ban as i was there watching it but it seems to be setting off their detection but when only running Wrotation i do not get the Logout System message or GM encounter.
  25. I use the move manager stuck count to detected stuck or not, if stuck count >n then execute recovery step in the quester step, but after step execute the stuck count always there, the quester always do the recovery step, anyone has idea about this?
  26. Version 1.0.162

    6 downloads

    Advanced Warrior Tank Fight Class for WRobot (WoW 3.3.5) Overview This advanced warrior tank fight class provides intelligent tanking capabilities with sophisticated positioning, threat management, and movement systems designed specifically for World of Warcraft patch 3.3.5 (Wrath of the Lich King). Key Features 🎯 Weighted Centroid Positioning Tank automatically faces the weighted center of all enemies Closer and more dangerous enemies have higher priority in positioning calculations Maintains optimal facing direction for maximum threat generation 🔄 Dynamic Enemy Grouping Detects when enemies are too spread out (beyond 140° cone) Automatically backs up to group scattered enemies together Enemies follow the tank, naturally reducing spread angle 📏 Adaptive Positioning Range Dynamic range calculation: 5-12 yards based on situation Accounts for number of enemies, casting threats, and enemy positioning Prevents premature function interruption during complex encounters 🛡️ Advanced Threat Management Prioritized taunt system (Taunt → Mocking Blow → Challenging Shout) Mass taunt detection for 3+ enemies within 10 yards Charge/Intercept for distant threats and casting enemies 🚶 Intelligent Movement System Advanced pathfinding with obstacle detection Line of sight checking and alternative route calculation Stuck detection with multiple recovery methods Manual control detection with absolute override protection Combat Features Rotation Priority System Emergency Interrupts - Shield Bash, Pummel, Concussion Blow Rage Management - Bloodrage when low on rage Multi-Target TPS - Shockwave, Thunder Clap, Cleave Single Target TPS - Shield Slam, Revenge, Devastate Debuff Maintenance - Sunder Armor stacks, Demoralizing Shout Defensive Abilities - Disarm, Shield Block Rage Dumps - Heroic Strike, Cleave (situation-dependent) Emergency Cooldowns 20% HP: Last Stand 30% HP: Shield Wall 50% HP: Enraged Regeneration 80% HP: Shield Block (automatic) Spell Reflection for casting enemies Party Protection Systems Vigilance Management Automatic healer detection and protection Emergency Intervene for healers under attack Dynamic Vigilance application to threatened party members Fear Breaking Automatic detection of fear effects Berserker Rage usage for fear immunity Comprehensive fear debuff database for 3.3.5 Configuration Options Movement Settings private const float IDEAL_DISTANCE = 3.0f; // Optimal enemy distance private const float MIN_DISTANCE = 1.5f; // Minimum distance before backing up private const float MAX_DISTANCE = 4.5f; // Maximum distance for positioning Cone Detection // Shockwave cone: 100° total (50° each side) if (angleDiff <= Math.PI / 3.6) // 50 degrees each side Spread Detection // Enemy spread limit: 140° total (70° each side) var maxAllowedSpread = (140.0 * Math.PI) / 180.0; Manual Control Protection The fight class includes comprehensive manual control detection: Keyboard Detection: W, A, S, D, Q, E keys Absolute Override: Any manual input stops all automated actions Fallback Detection: Movement speed analysis if keyboard detection fails Combat Awareness: Manual control respected even during combat Auto-Systems Auto-Targeting Intelligent target prioritization based on threat level Healer protection priority system Distance and casting enemy considerations Smooth target switching with hysteresis Auto-Buffing Commanding Shout priority (if known) Battle Shout fallback system Dynamic buff duration monitoring Party-wide buff management Auto-Looting Intelligent corpse tracking system Combat state awareness Distance-based loot prioritization Memory management for processed corpses Installation Instructions Copy the fight class code into a new .cs file Place in your WRobot FightClass folder Select the fight class in WRobot settings Configure any desired parameters Start bot and enjoy intelligent tanking Compatibility WoW Version: 3.3.5 (Wrath of the Lich King) WRobot Version: Compatible with current versions Language: C# with legacy syntax for older WRobot compatibility Performance Considerations Timer System Efficient timer-based checks prevent spam Configurable intervals for different systems Minimal CPU overhead during operation Cache System Smart object caching reduces API calls Periodic cache refreshing for accuracy Memory-efficient enemy and party tracking Thread Safety Proper locking mechanisms for movement coordination Thread-safe timer implementations Coordinated priority system for multiple movement functions Advanced Features Pathfinding System Line of Sight: TraceLine integration for obstacle detection Alternative Routing: WRobot PathFinder integration with optimization Stuck Recovery: Multi-stage unstuck system (Jump → Strafe → Backup) Obstacle Classification: Smart categorization of movement challenges Position Analysis Spread Calculation: Real-time enemy positioning analysis Centroid Weighting: Priority-based center calculation Facing Optimization: Minimal rotation for maximum efficiency Range Adaptation: Dynamic positioning range based on encounter complexity Troubleshooting Common Issues Tank not moving: Check manual control detection settings Erratic positioning: Verify enemy cache refresh rates Missing targets: Confirm auto-targeting priority weights Buff management: Check party member detection range Debug Features The fight class includes extensive logging: Movement decision logging Threat management notifications Emergency cooldown alerts Target switching information Credits Developed for the WRobot community with focus on intelligent automation and player experience enhancement. This fight class represents advanced tanking automation while maintaining respect for manual player control and game mechanics.
  27. if the character has not moved for a period of time, switch the chat channel to General or World and send a "1". How should I write this code? I hope you can all provide more help. Thank you again.
  1. Load more activity
×
×
  • Create New...