dropped_obj it still a type path, though, as you're setting it to one, then never modifying it, therefore it remains as one throughout the proc - pretty simple stuff.
While your new() call is creating an appropriate object, you're not using it at all throughout your proc, effectively discarding it, since you're not even using the reference new() returns to the new object for anything. Had you not given it a location, it would've been immediately deleted by the garbage collector.
Okay I decided to redo the coding. Before I use the following as reference, I need to fully understand it.
Kaioken wrote: obj/item Where the flip are you getting XYZ from? Objects.dm:88:error:XYZ:undefined var |
Okay I think I'm making a little progress >.<
obj/Items It gives me a runtime error saying it can't make obj type "/obj/Items/Weaponry/Knife/Bronze" (without the quotes). |
Right, I'm back now for a while.
Mizukouken Ketsu wrote: Where the flip are you getting XYZ from? You're kind of misunderstanding it there. XYZ is simply a stand-in intended for replacement, not an actual var... just a figure. You're supposed to insert 'what's supposed to be there' instead, in your code. Typically enough, since you're dropping an object, you'll want to set the dropped_obj to a new object of the same type of the object being thrown (and set its amount), unless the amount that is being dropped is the total amount, in which case you would of course set it to the dropped object itself to be moved, since creating a new one isn't necessary in that case. |
new dropped_obj(usr)