Skip to content

feat: add item converter tool, link to minimessage viewer#358

Merged
olijeffers0n merged 9 commits into
mainfrom
tools
May 3, 2024
Merged

feat: add item converter tool, link to minimessage viewer#358
olijeffers0n merged 9 commits into
mainfrom
tools

Conversation

@MiniDigger
Copy link
Copy Markdown
Member

No description provided.

Comment thread docs/misc/tools/item-command-converter.mdx Outdated
Comment thread docs/misc/tools/minimessage-web-editor.md
Copy link
Copy Markdown
Contributor

@Leguan16 Leguan16 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe move the tools section all the way down to the bottom?

Comment thread docs/misc/tools/index.mdx Outdated
@olijeffers0n
Copy link
Copy Markdown
Member

Maybe move the tools section all the way down to the bottom?

It is standard for us to put categories at the top

Copy link
Copy Markdown
Member

@kennytv kennytv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to make sure this isn't merged early: Needs to wait on more backend changes + it should get a dropdown for switching from the default Command to Item argument and Component argument with their different endpoints

@kennytv
Copy link
Copy Markdown
Member

kennytv commented Apr 22, 2024

The button effect fadeout looks a bit weird with the text briefly becoming gray and then white again. The boxes should also be a bit larger since the main use here is for longer commands

Comment thread src/components/ItemCommandConverter.tsx Outdated
@olijeffers0n olijeffers0n self-assigned this May 3, 2024
@olijeffers0n olijeffers0n merged commit 177956c into main May 3, 2024
@olijeffers0n olijeffers0n deleted the tools branch May 3, 2024 16:12
sowelipililimute pushed a commit to sowelipililimute/docs that referenced this pull request Sep 7, 2025
After many headaches trying to follow the mapping guide as written and
not understanding why it's not working properly, I am humbly offering
these updates to make it easier for people like me who are just starting
on SS14 mapping to understand what's going on:

- Map ID needs to be relatively high to avoid colliding with existing
IDs. I've heard that most people just straight up use 1000, so updating
all the IDs to that to establish best practices (+ explainer as to why)
- loadmapacts is deprecated, it is now mappingclientsidesetup
- Trying to be a bit more clear how to force your map and start it both
on Tools and Release build
- Adding the power command to the quick setup, since it's extremely
useful in most cases
- Explain that saved maps go into the Content.Server folder more
clearly, and you have to manually move them to Resources/Maps later.
- Explain that the Content.Server saved map has to be manually deleted
later on, or it will persist.
- Very slightly improve the explanation of the map image tool to make it
clear where you need to run it, especially if you don't use VS.
- Update the pipe color hex codes to the ones actually used on the live
version. Those "muted" pipe colors have not been used for a long time
and it's impossible to find the hex codes otherwise.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants