========================================================================
ICEBOX: Low-Priority Ideas
------------------------------------------------------------------------

  ####   #####    ####      #    #       ######  #####    ####
 #       #    #  #    #     #    #       #       #    #  #
  ####   #    #  #    #     #    #       #####   #    #   ####
      #  #####   #    #     #    #       #       #####        #
 #    #  #       #    #     #    #       #       #   #   #    #
  ####   #        ####      #    ######  ######  #    #   ####

- Falling_node is a train-wreck and needs to be rebuilt.
	- Attempts to monkey-patch it have still left fundamental problems.
	- Falling nodes can sometimes end up occupying the same space and
	  clobbering each other.
	- Search upward (up to starting height) for place to settle?
	- If settling fails, convert to item and bounce/eject?
	- Need to refactor out separate hooks for things like settling detection,
	  settling commitment, etc so downstream mods can tweak.
	- Arguably item_entity needs similar care.

- Wandering fluids API for concrete, glass?
	- Configurable setting for generation count multiplier.

- Lens strobing rate limiting of some kind?
	- Require cool-downs after a lot of toggling?
	- Could this be an accessibility issue?

- "Smart" optics placement?
	- Pick initial rotation automatically to have the most utility
	  according to some heuristics.
	- May involve expanding or redesigning the optics API
	  significantly...?

- Make separate walkable/non-walkable stack nodes.
	- Should sticks and eggcorns be non-walkable?

- Code Quality.
	- Scripts to validate dependency graph.
		- Tag deps directly in code at place of use.
		- Auto-generate mod.conf / depends.txt
	- Scripts for automatic metapackage mods?
	- Git hooks (and git hook setup scripts)?

- API Cleanup
	- Utils
		- Box mueller (and repeated box mueller sum) and exporand
	- Break up the nc_api monstrosity.
		- nc_api_base to create _G.nodecore and include for all.
		- nc_api metamod that just depends on ALL other api's.
		- nc_all metamod for 3rd party mod authors...?
	- Heat API
		- Unified heating/cooling number from env.
		- Proper API for burning up items
			- on_burn?  burns_to?
		- Unify heat transformations into recipe system with
		  cooking recipes?
	- Unify nc_items and visinv API.
		- Stack nodes are "special", get first-class support.

- Make neighbor/distance calcs consistent.
	- We're using scan_flood in some places, face checks in others,
	  and find_nodes_in_area (cuboid) in others.
	- Diamond shape would be most consistent.
	- Should require face touching, not diagonal.

........................................................................
========================================================================