Makes stack_trace error message a little more descriptive.

What's worse than vagueposting is vagueposting in runtime logs at spam rate of 36000 messages per hour.
This commit is contained in:
Verkister
2023-05-10 15:11:10 +03:00
committed by GitHub
parent 6239d377ea
commit 10404c83ed
+1 -1
View File
@@ -241,7 +241,7 @@
//Ensures that code dealing with stacks uses the same logic
/obj/item/stack/proc/can_use(var/used)
if(used < 0 || (used != round(used)))
stack_trace("Tried to use a bad stack amount: [used]")
stack_trace("Tried to use a bad stack amount: [used]. Location: [src.loc] ([src.x],[src.y],[src.z])") //CHOMPEdit
return 0
if(get_amount() < used)
return 0