Closed this issue 3 months ago · 1 comments
Fixed in the latest PR
Thank you, @feeops, for pointing out the incorrect variable in the README. I sincerely apologize for the oversight, and I’m happy to inform you that the issue has now been corrected.
