remove "mushroom" from the names of crimson fungus and warped fungus #3406

Merged
ancientmarinerdev merged 2 commits from SmokeyDope/MineClone2:change_fungus_name into master 2023-02-09 19:22:32 +01:00
Member

The names of crimson fungus and warped fungus are incorrect. Currently they are called "crimson fungus mushroom" and "warped fungus mushroom". "mushroom" should not be there.

Testing

go into creative and pull up the items. What are they called? you'll probably see "mushroom", at the end.

The names of crimson fungus and warped fungus are incorrect. Currently they are called "crimson fungus mushroom" and "warped fungus mushroom". "mushroom" should not be there. ### Testing go into creative and pull up the items. What are they called? you'll probably see "mushroom", at the end.
Contributor

The change makes sense. The downside is that with this we won't be able to bring up all of these in the creative search results by typing "mushroom". So having "Mushroom" in the name wasn't the right solution, just one of convenience.

If possible, we should introduce a tag/property for items, so we can have the right names, but also easily find similar items. I recently assumed "fish" would bring up all the fish-related stuff in creative mode, but that wasn't the case. :)

The change makes sense. The downside is that with this we won't be able to bring up all of these in the creative search results by typing "mushroom". So having "Mushroom" in the name wasn't the right solution, just one of convenience. If possible, we should introduce a tag/property for items, so we can have the right names, but also easily find similar items. I recently assumed "fish" would bring up all the [fish-related stuff](#3276) in creative mode, but that wasn't the case. :)
Author
Member

I like that idea, something similar to groups but explicitly for creative search phrases. something like
creative_search = S{"plant", "mushroom", "decoration", "nether"}

edit: or just put the names in the tool tip like so

	_tt_help = S("Crimson fungus is a mushroom found in the nether's crimson forest."),
	_doc_items_longdesc = S("Crimson fungus is a mushroom found in the nether's crimson forest."), 

Sometimes I feel like a big dummy haha. TY michieal and PrarieWind!

I like that idea, something similar to groups but explicitly for creative search phrases. something like creative_search = S{"plant", "mushroom", "decoration", "nether"} edit: or just put the names in the tool tip like so ``` _tt_help = S("Crimson fungus is a mushroom found in the nether's crimson forest."), _doc_items_longdesc = S("Crimson fungus is a mushroom found in the nether's crimson forest."), ``` Sometimes I feel like a big dummy haha. TY michieal and PrarieWind!
Author
Member

Im not sure how to impliment something like that, but if someone figures it out I am willing to commit the time to go through and add that stuff to nodes

Im not sure how to impliment something like that, but if someone figures it out I am willing to commit the time to go through and add that stuff to nodes
SmokeyDope closed this pull request 2023-02-06 02:28:16 +01:00
SmokeyDope reopened this pull request 2023-02-06 02:49:29 +01:00
Author
Member

Oh so thats what the close button does lol whoops

Oh so thats what the close button does lol whoops
Member

Yeah, don't do that. lmao!

Yeah, don't do that. lmao!
Member

I like that idea, something similar to groups but explicitly for creative search phrases. something like
creative_search = S{"plant", "mushroom", "decoration", "nether"}

Search "job" in creative. Note that the Lectern comes up. Hover over the lectern, to see where the word "job" is at. Apply that to existing items that should be tagged. Thank me when done. :D

edit: to be fair, I did say how to do it here.

> I like that idea, something similar to groups but explicitly for creative search phrases. something like > creative_search = S{"plant", "mushroom", "decoration", "nether"} Search "job" in creative. Note that the Lectern comes up. Hover over the lectern, to see where the word "job" is at. Apply that to existing items that should be tagged. Thank me when done. :D edit: to be fair, I did say how to do it [here](https://git.minetest.land/MineClone2/MineClone2/issues/3276#issuecomment-57967).
First-time contributor

Put mushroom in the tooltip.

~~Put mushroom in the tooltip.~~
Author
Member

Im on it, thanks for the recommendation

Im on it, thanks for the recommendation
ancientmarinerdev approved these changes 2023-02-09 02:28:15 +01:00
ancientmarinerdev left a comment
Owner

It looks good to me. You haven't been around too long, but so far, I think you are a fun-gi!

It looks good to me. You haven't been around too long, but so far, I think you are a fun-gi!
ancientmarinerdev added this to the 0.83.0 - Safe and Sound milestone 2023-02-09 04:22:03 +01:00
ancientmarinerdev force-pushed change_fungus_name from 8ea869e930 to dfbee5cb93 2023-02-09 04:22:26 +01:00 Compare
First-time contributor

@SmokeyDope would you like to hit the green create merge commit button?

@SmokeyDope would you like to hit the green create merge commit button?
Ghost approved these changes 2023-02-09 19:17:16 +01:00
Ghost left a comment
First-time contributor

Looks good to me 👍.

Looks good to me 👍.
ancientmarinerdev merged commit 428b1b2c12 into master 2023-02-09 19:22:07 +01:00
First-time contributor

Nothing like taking the fun out of it. I was really excited to merge my first pull request when I got merge privs. :(

Nothing like taking the fun out of it. I was really excited to merge my first pull request when I got merge privs. :(

@SmokeyDope would you like to hit the green create merge commit button?

I'm not sure if he has the access at present. He has contributor status. I think only developer status has that.

To be honest, I would prefer to be the one doing the merging. I want to know what is going in and when. I want to make sure it's tagged correctly and if multiple people are working on something, I'd prefer the bigger one going in first, especially if the PR was created first. It's harder to deal with merge conflicts for bigger branches.

I had meant to merge in yesterday but the conflict checking is a little slow atm.

> @SmokeyDope would you like to hit the green create merge commit button? I'm not sure if he has the access at present. He has contributor status. I think only developer status has that. To be honest, I would prefer to be the one doing the merging. I want to know what is going in and when. I want to make sure it's tagged correctly and if multiple people are working on something, I'd prefer the bigger one going in first, especially if the PR was created first. It's harder to deal with merge conflicts for bigger branches. I had meant to merge in yesterday but the conflict checking is a little slow atm.
SmokeyDope deleted branch change_fungus_name 2023-02-09 20:57:22 +01:00
Sign in to join this conversation.
No reviewers
No project
No Assignees
5 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#3406
No description provided.