sztest/nodecore-cd2025
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
nodecore-cd2025/docs/issues.txt

60 lines
2.4 KiB
Plaintext
Raw Normal View History

Doc restructure, cleanup. Instead of a single queue backlog/icebox setup, split into large dev spikes and issue/cleanup stuff. I've been doing a sort of "tick-tock" development cycle in practice so far. Sometime cycles are "tick" where I add a major feature, like shelves/totes, lode metallurgy, etc. Others are "tock" cycles where I make a lot of small releases to clean up issues accumulated from prior work. The new backlog format will help keep these separated better.
2019-03-03 11:30:30 -05:00
========================================================================
ISSUES: Bugs, Cleanup and Refinements
------------------------------------------------------------------------
Documentation updates, new player guide interface. Also restructured the player_inv/player_setup thing AGAIN. Now setup is all rules and inv is all interface.
2019-03-05 19:20:38 -05:00
#### ##### #### # # ###### ##### ####
# # # # # # # # # # #
#### # # # # # # ##### # # ####
# ##### # # # # # ##### #
# # # # # # # # # # # #
#### # #### # ###### ###### # # ####
Add "stasis" option and command. This freezes many things that normally happen automatically in the world, including most ABMs and AISMs, and a few other custom step logic items like the player "hot potato" logic. This can be used for "creative mode" purposes to setup a complex build without it running itself away from you, and for texture pack authors, to have time to see things that are normally transient or difficult to observe because of the effects they have on nearby things or players.
2020-01-10 06:26:07 -05:00
- Item ent merge should use logic consistent with nodecore.stack_merge,
which handles item families.
- Flammables should respond via AISM when bathed in fire or igniting
liquids like molten glass or rock.
Notes from discord.
2020-01-19 17:44:33 -05:00
- Need to find a way to make AISMs work with falling_node.
- Create ItemStack, run hooks, try to convert back to node
(assume node and item meta map 1:1) and if it fails then
spawn an item_ent.
- Need this for amalgamation remelting.
- Would it make sense to unify the item and falling_node ents?
Notes sync from Discord.
2020-01-07 06:56:11 -05:00
- Can we automatically dump a TP overrides.txt file?
- Move this, and translate hook, to a chat command?
- Quicker optic path updates.
- Record which nodes are blocking optic paths, and which are
used by optic paths, in-memory, for quicker recalcs?
Notes from discord.
2019-12-17 19:09:27 -05:00
- 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.
Notes from discord.
2020-01-19 17:44:33 -05:00
- Offline grass spreading.
- Use new nodecore.soaking_abm_push API.
Notes cleanup.
2019-12-31 10:35:19 -05:00
- Will have to do a lot of performance testing.
Small pos key calc optimization.
2020-01-10 21:11:52 -05:00
- Replacement for mkreg, a.k.a. register_generic():
- Allow lazy registration, i.e. a register method that can
register for things not yet defined, and allow later registration
of the registration definition that will pick up those missed.
- Allow unregistering things...?
Notes sync from Discord.
2020-01-07 06:56:11 -05:00
- Should ash and derivatives have a fertilizing effect?
- Maybe wet/tacky stuccos?
Notes from discord.
2020-01-19 17:44:33 -05:00
- Unify sponge growth logic so it can be used for mapgen, to ensure
that spawned sponges match naturally-grown ones?
Update notes from Discord.
2019-11-16 19:52:22 -05:00
- Design doc needs another shakedown.
Revert "Scaling overhaul." While this makes scaling a little easier to do, it still doesn't fix the fundamental problem of scaling being distracting and too easy to trigger accidentally. The "pummel" version of scaling caused some confusion when one player accidentally triggered it trying to figure out how to get lode out of lode ore. The current one triggers accidentally all the time just from tabbing out of a game with it running (e.g. it isn't paused in multiplayer) leaving the character staring at a wall. While such a player WOULD have opportunity to find handholds in the wall, we aren't differentiating between a player who's scrutinizing a surface from one staring off into space. The scaling needs to be made harder to trigger accidentally, like reinstating the need for an empty hand. Using a right-click action may also help distinguish it from pummelng recipes. Removing this from the alpha branch so players don't get too accustomed to this functionality and then have it change AGAIN. This reverts commit 943604cf9588a316dce19e0a60a4219b52c4d905.
2019-10-24 20:16:37 -04:00
Door recipe simplification. - No graphite lubrication needed. - Just insert pin instead of pounding it in. - Pins must be inserted into end face. - Node will not spin from using pin on wrong face.
2019-10-27 08:34:33 -04:00
- Consider updating tote recipe.
Fix broken lux ore hard strata.
2019-09-15 07:32:06 -04:00
Doc restructure, cleanup. Instead of a single queue backlog/icebox setup, split into large dev spikes and issue/cleanup stuff. I've been doing a sort of "tick-tock" development cycle in practice so far. Sometime cycles are "tick" where I add a major feature, like shelves/totes, lode metallurgy, etc. Others are "tock" cycles where I make a lot of small releases to clean up issues accumulated from prior work. The new backlog format will help keep these separated better.
2019-03-03 11:30:30 -05:00
........................................................................
Some minor API cleanup (celebrating 5.0 release).
2019-03-04 19:33:55 -05:00
========================================================================
Reference in New Issue Copy Permalink