Closed WanderingFox closed 4 years ago
I think it should be directed at bagnon, the error isn't comeing from baggins code. The only reason baggins shows in that error is our copy of LibGratuity gets loaded first because our addon gets loaded first because our name. If theres no error with just bagnon then im guessing they use a modified version or you are.
Getting a C stack overflow in LibGratuity-3.0 after updating to the latest version of Baggins when attempting to open Bagnon.
Disabling baggins makes bagnon immediately start working, as does rolling back to an old (admittedly manually patched) version.
If this should be directed at bagnon's maintainer instead, please feel free to let me know :)