Ace3 (orig) Error #48


  • Waiting
Open
  • badco54 created this issue Oct 24, 2017

    I am prevented from logging out or exiting the game via the Escape menu or using /camp or /quit.

  • badco54 added a tag Waiting Oct 24, 2017
  • Wig0r posted a comment Oct 25, 2017

    Find

    	 -- Hook the functions that need hooking
    	 self:Hook("Logout", true)

     Replace with

    	 -- Hook the functions that need hooking
    	 -- self:Hook("Logout", true)
    	 self:RegisterEvent("PLAYER_LOGOUT", "Logout")
    

     This disables the WRONG way to do stuff and replaces it with the right way to do it.

  • zaph0n posted a comment Oct 25, 2017

    I commented out the Hook functions and replaced with the PLAYER_LOGOUT event, seems to be working so far.  Just curious why this would stop working in 7.3.2 if it was truly deprecated.  And I'm sure AllPlayed isn't the only addon to use AceHook.

  • Hrazmadul posted a comment Oct 25, 2017

    I changed the quit event aswell from

    self:Hook("Quit", true)

     

    to

    self:RegisterEvent("PLAYER_QUITING", "Quit")

     

    as I was getting error when clicking quit when online on a character.

  • nevcairiel posted a comment Oct 26, 2017

    I don't hink PLAYER_QUITING is actually an event.

  • Hrazmadul posted a comment Oct 26, 2017

    Well I found it on this page and tried it and got no LUA complaints.

    http://wowprogramming.com/docs/events

    http://wowprogramming.com/docs/events/PLAYER_QUITING


    Edited Oct 26, 2017
  • KahunaxTXC posted a comment Dec 12, 2017

    I've updated my .lua to note the changes above. I still get the error message if I attempt to Exit the game while logged in. If I log out to the character screen & then hit the Back button...then Quit...I am able to exit WoW. Is there a work around for this situation?

  • Riothamus0522 posted a comment Feb 16, 2018

    For those of us whom are simply looking for the main add-on to be updated and not do coding stuff ourselves, in laymans terms will this add-on receive an overall update so that it can be used again (not having the Blizzard UI error that forces disabling the add-on every time), or is the only 'use' going to be having to individually each going into our files and changing the coding?

     

    This is an add-on I've use for longer than I can remember, I'd dare say over a decade, and it would be sad if it's time to part because of the coding not being appropriate rewritten to compensate for Blizzard's requirements/restrictions.

     

    Thanks!

  • serious2 posted a comment Sep 14, 2018

    The addon is fixed for now. Look here

    https://www.wowace.com/projects/all-played-laotseu/issues/53


To post a comment, please login or register a new account.