======================================================================== -----===== PUBLIC CONTRIBUTION WISHLIST =====----- ------------------------------------------------------------------------ Remember, check out the CONTRIBUTING file for guidelines on contributing to the project! - Testing and bug reports! - Translations: - https://nodecore.mine.nu/trans/projects/nodecore/core/ - Help (PRs and/or advocacy) with Minetest engine issues: - Minor game-breakers: - #9377: This causes some annoyances when handling lux tools, and makes a certain mechanic blatant when it's intended to be subtle. - #7876: Causes a damage flash when a new player joins, or a player from before 2020-02-19 when max HP was changed. - #8952: This causes hidden bases and other items to be visible through walls when ent/player transfer distance is high; when low, instead it causes players/ents to be invisible even when terrain is loaded and visible, causing distant player activity to look like poltergeists. - Blocking new features: - #11404: Desktop/mobile controls lack parity, so certain input combinations (like sneak+punch) cannot be used for things that are gameplay-essential. This limits input expressivity and requires awkward inputs to work around, and is a minefield for potential discrimination problems due to the difficulty of ensuring that all future input design takes this into account. - TBD: Bone attachment axes invert if there is any animation on that bone/axis. This is blocking the head pitching feature. (MTG #2547, but it's probably an engine bug) - #9912: Engine should provide a standard way to make digparticles that doesn't depend on using [combine and knowing exact source texture size (breaks texturepacks). - Internal/annoyance: - #9934: This bug is causing us to maintain a workaround in NodeCore which is fragile and keeps breaking, leading to significant network load for some clients. - #6963: If this is implemented, we may have a more efficient way to handle "visinv" nodes, i.e. stacks, storage boxes, and other container nodes. - Help with documentation - Improvements to the in-game guidance, esp. for onboarding new players, are wanted. Ideally we want to offer a spoiler-free experience by default, but want players to have options/resources in the event they can't figure something out. - Advising players where they can find external resources, or other sources of help, such as wikis, youtube, chatrooms, multiplayer servers, etc. - Work on improving the nodecore wiki itself. - Improved versions of any art assets (sounds, textures, models). - Yet another overhaul of the player model, this time to support headanim (animate head bone to show player pitch) https://github.com/LoneWolfHT/headanim/blob/master/init.lua - All textures for base inclusion should be 16x (keep high-def textures to texture packs). Note that textures larger than 16x are allowed (and already used) in the game for textures that "spill over" into neighoring spaces, but the spatial resolution of 16 pixels per node is maintained. - It must be practical to maintain a consistent style for other assets, including future related ones, or the content being reworked should be mature and stable, independent of other content areas, and the new textures should mesh reasonably well with the existing style. - Alternatively, publish your mods, texturepacks, or soundpacks directly to the community, via ContentDB. - Replacements for nodeboxes and meshes that render faster (i.e. better FPS preservation when tons of them are around) on most or all systems are wanted. - Publicity and player content: - Help spread NodeCore! Share your experiences, screenshots, videos and streams! - Let the developers know if you have shared something about NodeCore, or would like guidance creating something to share. ........................................................................ ========================================================================