nodecore-cd2025/docs/issues.txt
2019-12-18 19:53:59 -05:00

87 lines
2.9 KiB
Plaintext

========================================================================
ISSUES: Bugs, Cleanup and Refinements
------------------------------------------------------------------------
#### ##### #### # # ###### ##### ####
# # # # # # # # # # #
#### # # # # # # ##### # # ####
# ##### # # # # # ##### #
# # # # # # # # # # # #
#### # #### # ###### ###### # # ####
- Hint updates:
- Press recipe witnessing?
- Rake.
- Glass tank.
- Optics states, e.g. active, shining, gated.
- Injury/burns?
- Full tote?
- Dirt->sand leeching
- Time for an audit again...
- Retest conservation of fuel at full strength, consider reinstating?
- Original nerf was actually due to shelf bug.
- Flammables should respond via AISM when bathed in fire or igniting
liquids like molten glass or rock.
- API for allowing mods to customize player texture.
- Maybe nodecore.register_on_player_textures(layers) where
layers is an array of entries, each having {name = "",
tile = ""} and returning a replacement array (or nil to use
existing).
- Maybe nodecore.update_player_texture(layers) and allow the
method to be intercepted.
- Consider checking for a nearby active player before running
"fast-evolving" ABMs that don't normally work offline, like fire
extinguishing/spreading?
- This would make gameplay more fair for those who tend to
go AFK suddenly and can't return for a long time.
- Probably should be using hash_node_position insted of pos_to_string
in many places where we don't support non-integer positions anyway
- CDB screenshot out of date.
- Update nc_reative dependencies!
- New optics
- Full tote
- Glass tank, lode crates
- Lux
- Torches
- Design doc needs another shakedown.
- Relax tree-trunk-chopping recipes.
- Climbing a tree to adze it from the top may be to much of a
logical leap.
- Offer a slower recipe from the side?
- Offer a recipe to dislodge a segment from the trunk?
- Consider updating tote recipe.
- Lux reaction cannot sense other lux inside totes.
- Consider making a unified API for HUDs
- Automatically track existing HUDs for players.
- Identify HUDs by name/ID.
- Upsert operation.
- TTL management.
- API for modifying/overriding nametag HUDs?
- Allow amending text/color attributes, blocking display, etc.
- API for recursing through embedded inventories, e.g. in totes.
- Player APIs:
- Texturing, for clothing mods.
- Physics/acceleration, for waterflow, conveyors, etc.
- When can we remove the issue7020 workaround?
- Node mesh improvements.
- Generic container/box model for shelves/tanks using 12 quads.
- Optimized/ retextured tote handle.
........................................................................
========================================================================