Add colors.txt file to tools/ #2953

Merged
Ghost merged 2 commits from add_colors_txt into master 2022-11-15 23:16:55 +01:00
Contributor

As provided by RankoSaotome on mcl2 discord

As provided by RankoSaotome on mcl2 discord
Member

Maybe we could make updating it a part of the release process?

Maybe we could make updating it a part of the release process?
Contributor

What does said "colors.txt" file do exactly?

What does said "colors.txt" file do exactly?
Member

What is this and how does it relate to colors.json in mcl_maps?

What is this and how does it relate to colors.json in mcl_maps?
Author
Contributor

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) .

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) .
Ghost force-pushed add_colors_txt from ad08f555aa to 51d4f075b2 2022-11-15 23:13:07 +01:00 Compare
Ghost approved these changes 2022-11-15 23:16:24 +01:00
Ghost merged commit 4255143087 into master 2022-11-15 23:16:55 +01:00
Ghost deleted branch add_colors_txt 2022-11-15 23:16:59 +01:00
Member

What does said "colors.txt" file do exactly?

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.)

What is this and how does it relate to colors.json in mcl_maps?

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.

> What does said "colors.txt" file do exactly? 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.) > What is this and how does it relate to colors.json in mcl_maps? 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.
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: VoxeLibre/VoxeLibre#2953
No description provided.