Rabbit 16 Posted April 30, 2019 (edited) Simple as that, using .lookup next after a .lookup creature query will return the result "You have no pending .lookup in memory." I know Azarchius has addressed before that it is just a visual bug, but typing .look creature Crow will not display https://www.wowhead.com/npc=67443/crow. So it is definitely not a visual bug. Edited April 30, 2019 by Rabbit Share this post Link to post Share on other sites
Rabbit 16 Posted April 30, 2019 (edited) It seems to be working currently. EDIT: 1 hour later it doesn't work anymore. Edited May 1, 2019 by Rabbit Share this post Link to post Share on other sites
Azarchius 212 Posted May 1, 2019 This is definitely, 100% the source of the lookup creature crashes. This has given me an idea. I will look into fixing this, as well as the lookup creature crashes (which is the source of some 70% of our crashes) for 735.4, which may be coming earlier than expected. Share this post Link to post Share on other sites
