mining satchels automatically collect ore if held in the hands, belt, or suit slot.
pulling an ore box with a satchel collects ore into the ore box instead of the satchel, and empties the satchel if appropriate.
hostile mining drones collect into ore boxes just like people would. Their collection checking view size is smaller.
mining satchels and ore boxes only update their contents hints if examined after it changes, rather than up to once a second regardless of changes.
various doubled messages removed.
removed various dm-land loops in favor of contents addition where it makes sense.
refactors atom/var/flags to atom_flags and area_flags
moves NOBLOODY, NOBLUDGEON, and PHORONGUARD to item_flags instead of atom_flags
corrects various misapplied flags
NB. In some cases we go from a more complex image() to a single icon_state string and I assume this works for every case but do not care to check because of the sheer scale of extra fiddly effort. Buyer beware, not my code.
Specific to mining turfs, but I imagine others might have this.
The reason we don't directly pull from 'icon' is to allow turf making folk to have some fun to play with it, make the icon change only on update, etc.
If preferred, icon_path var can just be set to grab the turf's base icon path, but I prefer the var imo.
* Begins work on Planetary meteors
* Work, clean meteor code.
* Continues work. Meteors now handle their own movement and launching.
* New meteor types, some added to waves. Large meteor type fully implemented.
* Fix and adjust for comments.
* get_tool_quality has numerical meaning
* Basic tools set tool quality
* Toolspeed is replaced by tool quality checks
* Addresses assorted results from live test
* Extra cleanup
* Adds cold walls & floors
woop
* adds dark ice
weee
* updates snow edges tooo
weee
* adds a temporary ice sand sprite
ver scary
* Fixed a weird one
* But why
* Cleans up footprints
* Adds a brown version of the rock I've made because
* Adds linter defines to repo.
* Uncomments linter defines already in the code.
* Resolves unreachable code linter errors.
* Nukes decade+ old syndie specops code except for computer since that's mapped in?????
* Resolves procs has no parent linter error.
* Proc signature fixes
* Bad comments
* "In" danger
* Type safety
* Implied nested list abuse
* Top level ..() usage
* Sleepy coder typos
* Invalid kwargs calls
* Pointless returns
* Linter hacks (see full message)
Byond doesn't care and it has no effect but linter doesn't like var/proc
for holding references to procs, despite that it's valid byond code.
Also, the linter seems to have serious issues figuring out relative
proc names. This commit is a sort of take-it-or-leave-it thing. It's not
required, it just cuts down on warnings, but this code is valid DM code.
* WHATEVER THIS IS
* Trick dreamchecker linter into ignoring this file's sins in it's weird use of vars
* Fix list decoration syntax - Its a list, not list of lists
- To declare that a var is a list you can `var/list/blah = list()` syntax or the `var/blah[0]` syntax. Both do exactly the same thing. But if you do `var/list/blah[0]` that is just like doing `var/list/list/blah = list()`
* Hopefully stops the ai holder subtype folder from going quantum and sometimes changes capitalization over time, and incidentally causing 20+ linter errors.
* Fixes unwrapped negated object in list linter error.
* Resolves colon-like list accessing linter error.
* Turns linter on in linter config.
* Fixes closet indentation properly and cleans up suit storage unit switch.
Co-authored-by: Aronai Sieyes <arokha@arokha.com>
Co-authored-by: Leshana <Leshana@users.noreply.github.com>
* The Deep Scan Device
adds new ore detector sprite and changes name to better fit the functionality
* Minor Grammatical Change
Removed capitalization of 'deep scan device'
