Current Skrell lore dictates that while these are the Skrell's true names, they take up names that are human or make their own names pronounceable to humans. Having the ability to randomly generate the Skrell name is ideal if you want to have a humanized Skrell name, whereas randomly generating a human name can be done off of a human slot.
* update_inv_ears() overlays left and right ears upon a "blank" icon. Unfortunately doing ```image("icon" = null)``` encourages BYOND to create an image of the current mob! So everyone's "ears" icon is actually their whole body, layerd on top of uniforms, hair, etc.
* Lets not do that. A transparant image is already in effects.dmi for this purpose.
Calls the final HUD update later (higher, in mob/death) since stat was not yet DEAD (2) when it was called before.
Also makes all mobs update the HUDs all life() ticks, so people who have ghosted and left a body have correct HUD readings. If this affects performance, sorry? ... It really shouldn't. Only carbons should have real HUDs to update. The rest are tiny little procs.
Removes limitation of being unable to join different colors of cable
Allows merging of different kinds of cable
Adjusts the color changing proc to be nicer as per Baystation12/Baystation#11645
I missed it! So I fixed it.
It could have been done with a bunch of "If you're SUPPOSED to be blind" or "If you're ASLEEP" but honestly this check should be in there anyway. P.sure people with tourettes don't randomly scream things while asleep.
Naked and trying to wear a rig, it will attempt to access w_uniform.inv_flags which will be null and runtime.
Moves shoe redrawing to uniform and suit update_inv code in update_icons, rather than in inventory.dm. update_icons already had code for this.
Previously, because noncritical robolimbs did not count for bruteloss or burnloss (per line 13 in human_damage.dm), nothing would ever cause robot limbs to call update_wounds() on the organs to clear wounds after repair. Furthermore, update_wounds ignored wounds on robotic limbs and edited early without even checking if it should remove them. This caused a problem.
This corrects this, and still exits early(er) in update_wounds() for robotic limbs, but makes sure there are no 0-damage wounds left and if there are, removes them.
As a 'backup', hitting a robolimb with a welder when there's nothing to fix will also call this proc, to catch any cases where someone has directly changed wounds or anything like that.
Also fixes spacing on robolimb damage examine text (get_wound_desc had spaces, but should not have in most cases), and added a message for having an open maintenance panel on a limb.
