Add colors.txt file to tools/ #2953
No reviewers
Labels
No Label
#P1 CRITICAL
#P2: HIGH
#P3: elevated
#P4 priority: medium
#P6: low
#Review
annoying
API
bug
code quality
combat
commands
compatibility
configurability
contribution inside
controls
core feature
creative mode
delayed for engine release
documentation
duplicate
enhancement
environment
feature request
gameplay
graphics
ground content conflict
GUI/HUD
help wanted
incomplete feature
invalid / won't fix
items
looking for contributor
mapgen
meta
mineclone2+
Minecraft >= 1.13
Minecraft >= 1.17
missing feature
mobile
mobs
mod support
model needed
multiplayer
Needs adoption
needs discussion
needs engine change
needs more information
needs research
nodes
non-mob entities
performance
player
possible close
redstone
release notes
schematics
Skyblock
sounds
Testing / Retest
tools
translation
unconfirmed
mcl5
mcla
Media missing
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: VoxeLibre/VoxeLibre#2953
Loading…
Reference in New Issue
No description provided.
Delete Branch "add_colors_txt"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As provided by RankoSaotome on mcl2 discord
Maybe we could make updating it a part of the release process?
What does said "colors.txt" file do exactly?
What is this and how does it relate to colors.json in mcl_maps?
I don't think making the release process even more complicated is a good idea. Plus this would require to take note of all nodes added as well (yk additionally to the stuff you already need to keep track of).
I think it's absolutely fine if whoever adds nodes or whoever uses minetestmapper adds missing colors (that's what it's for @MrRar) .
ad08f555aa
to51d4f075b2
It is used for the Minetest Mapper program. The mapper program uses it to color pixels in the output image that it makes, after scanning all of the nodes that you've explored / loaded. (Ie, that the engine has generated / changed.)
Not related to colors.json in mcl_maps, though we might want to be update that as we add new nodes. Though, depending on formats, we might be able to use the colors.txt to quickly update colors.json.
the minetest mapper program has a utility to generate a colors.txt, but it will usually use the one in the main minetest dir in your /usr/bin/ dir. Problems with this, though, include the fact that it does NOT take into account for how we color the textures in code. A primary example of this is that the grass is grey, even though it's green when the node is registered.
Another good example is that things like water logged nodes are going to be off as they are multi-textured.
That said, this is a popular utility that players use to see where they have been and have explored.