Jump to content

Zer0

Elite user
  • Posts

    213
  • Joined

  • Last visited

Posts posted by Zer0

  1. It's a known issue. When you get off a mount (or a taxi for that matter), or after a loading screen, there are a few frames during which your pet hasn't spawned yet. If the FC catches one of these frames, it will think the pet is dead and resummon.

    One way to prevent this issue is for the FC to start the cast and then regularly check if the pet is alive during the cast. I think I implemented something like that in the wotlk AIO (or tbc, can't remember). I don't think that's feasible with a XML FC.

  2. Not that I know of. Communication between wRobot modules (product/FC/plugins) or between bots is not possible with simple code.

    Your initial idea to trigger a setting change using the client's chat is actually the best suited idea for this case I think. If your plugin is open source, then you should try and modify it directly.

  3. If I understand correctly, you're trying to have a group of 2 do a series of quests using the quester product where one member does the quest, and the other follows, and you want to be able to switch those roles at runtime.

    I'm not very familiar with the quester, but that seems very difficult to do, if possible at all. You might be better off making your own product at this point.

    I created 2 video tutorials for beginners, plugin and product, maybe that will help you.

     

  4. As Matenia said, from their website

    Quote
    Can I use an existing 2.4.3 client?

    No. To play on our realms you'll need a 3.3.5a client with additional patches.

    Can I use an existing 3.3.5a client?

    Yes. To do so, simply install the launcher and proceed to click on the 'Locate the game' button. Then, select the folder where your 3.3.5a client is located. Keep in mind our patches will also convert the client to an Endless-only client, so making a backup is advised.

    I'm quite surprised they would use a wotlk client for a TBC server and I'd be very curious to know what these "patches" do exactly.

    As for the Wholesome TBC Fight class, I can confirm that it works on a regular wotlk client. No idea about the endless one. You should probably test it with the trial version.

  5. Almost all your comparison operators seem to be reversed. 

    for example:

    if(FlashHeal.KnownSpell && FlashHeal.IsSpellUsable && FlashHeal.IsDistanceGood && ObjectManager.Me.HealthPercent > 50)
    {
      FlashHeal.Launch();
      return;
    }

    means that Flash Heal will be used when your health percent is above 50%. You want the opposite:

    if(FlashHeal.KnownSpell && FlashHeal.IsSpellUsable && FlashHeal.IsDistanceGood && ObjectManager.Me.HealthPercent < 50)
    {
      FlashHeal.Launch();
      return;
    }
  6. I have just tried with a brand new WRobot install and still had the freeze on login screen, even with one single instance. 

    But since you told me you weren't able to reproduce the bug, I thought it might come from my WoW client, so I tried with another one that was sitting on my computer, the client from Sunwell. No more freezes. Just to confirm I tried to launch my 5 instances with this client about 15 times and had no freeze. So that's it, the problem was the WoW client. Big relief. Thanks for your help.

    If anyone has this issue, try downloading another WoW client.

  7. image.png.c0a1fa7514e1309768ca724add7afdf4.png

    These are my settings. To be honest, I've changed them so many times to try and fix the issue that I have no idea if it's right.

    I have tried deleting my wow cache, it didn't help.

    For the option "Lock when launch.... (only this relogger process)" , it was off. I turned it on and tried again, but I still got one freeze.

    The freeze can happen even if I only launch one single instance.

  8. My only wow addon is Recount. I don't have any particular antivirus. I play on a local server, so no proxy or VPN either. My wrobot install is not new, but still fairly recent.

    image.thumb.png.514d9c4ae3715781a67e0981c2c34d8c.png

    I don't know if this can help, but this a screenshot of an example I just took. I clicked "Start Checked" in the relogger. All wow/bot instances started, except the one you see frozen on the login screen. What happens next is that after 30 seconds, the client is detected as hanging, gets closed and restarted. It is usually not guaranteed that it doesn't freeze again after restart.

    The freeze can happen for none, or multiple instances. It seems completely random.

    The issue always happens at the same moment (when it's time for the bot to enter the account login/password).

    Hit me up on discord if you need more info. I can stream it to you if needed.

  9. I have 5 tasks ticked in the relogger, one for each of my characters. The way I start them is by pressing "Start Checked". That's pretty much the only way I use the relogger.

    When I stop the relogger, I simply press "Stop and Kill all", which closes everything (game & bot)

    `If I stop/start manually can I reproduce this problem?`

    Not sure what you mean. If you mean the buttons called "Start/Stop" at the left of the task, then it's the same issue. Even if I start one single task, it has a chance to freeze.

    I'd say it happens ~30% of the times overall.

  10. Hi, 

    I'm developing a product that requires me to stop/start the Relogger quite often. The relogger launches 5 WoW instances (WotLK).

    My problem is that oftentime, 1, 2, or 3 of the wow clients freeze during the loading screen. Then it takes roughly 30 seconds for the Relogger to detect that a process is hanging and to restart the faulty client. As you can imagine, it's slowing me down quite a bit. The -nodx argument seems to fix this specific issue but then consistently causes crashes during runtime. Apparently, I'm not the only one experiencing this.

    Is there any solution at all?

  11. I'm not entirely sure it will work for vanilla, since I've used it on TBC/Wotlk, but even then, there's no easy way to do this. The only way I know to read item stats is to create a LUA Frame, set its hyperlink to the item link you want to check, and read its regions.

    You can check the LUASetup() method to get an idea how this works here https://github.com/Wholesome-wRobot/Wholesome-Inventory-Manager/blob/master/Helper/Toolbox.cs

    After you've ran this setup, all you need is to call is ParseItemInfo(itemLink) in LUA to get your item stats. You'll have to adapt the code to whatever you want to do, obviously.

  12. You can check for your pet's spell cooldown like so:

    local start, duration, enable = GetSpellCooldown(PET_SPELL_INDEX, 'pet') 
    return (duration - (GetTime() - start)) * 1000

    This returns the spell cooldown in milliseconds. The spell is ready when it returns a value lower than 0. You'll need to replace PET_SPELL_INDEX with i in your case.

  13. Agreed with @Matenia. Having a separate manager that records the state of the ObjectManager on each pulse is ideal, not only because your rotation can reuse these info very fast, but also besaue it gives you a reliable "snapshot" of the game state. There are pitfalls to this and it requires some thorough performance monitoring.

    It's definitely overkill for a simple rotation, so I think the dictionary solution at the begining of your iteration is a fine compromise if you check on a lot of buffs.

×
×
  • Create New...