Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Localizable craftmenu #32339

Closed
wants to merge 19 commits into from

Conversation

Ertanic
Copy link
Contributor

@Ertanic Ertanic commented Sep 20, 2024

About the PR

The name, description and icon of the target crafting items are now taken directly from the prototypes.

Depends on space-wizards/RobustToolbox#5466.

Why / Balance

Technical details

Due to the fact that prototypes are read only on the server (and I don't know how to make them read on the client), I have to call a network event when initializing ConstructionSystem. The server traverses the ConstructionPrototype collection once and creates a ConstructionPrototype.ID-to-EntityPrototype.ID map, which the client then works with.

To take sprites directly from the prototypes, ItemList has been replaced by ListContainer, which uses EntityPrototypeView.

Fluent keys were used to localize GraphStep. Therefore, the names of tag and material steps, which are used directly in the construction menu, have been moved to ftl files.

The MaterialConstructionGraphStep (is specified in StackPrototype) passes the necessary amount of material so that it can be translated using selectors. Especially relevant for the Slavic language group.

Media

Requirements

Breaking changes

Changelog

  • tweak: The name, description and icon of the target crafting items are now taken directly from the prototypes.

@slarticodefast
Copy link
Member

Wouldn't that cause problems with things like secret walls that have a different name?

@Ertanic
Copy link
Contributor Author

Ertanic commented Sep 20, 2024

Wouldn't that cause problems with things like secret walls that have a different name?

Very likely. But exactly the secret door in the prototype itself is referred to as a solid wall.

image

@slarticodefast
Copy link
Member

Yeah, that's a problem, you won't know which one is which if you don't know the recipe. Maybe add an optional translation string to the crafting menu entry that overrides the prototype name if necessary.

@chavonadelal
Copy link
Contributor

chavonadelal commented Sep 20, 2024

Yeah, that's a problem, you won't know which one is which if you don't know the recipe. Maybe add an optional translation string to the crafting menu entry that overrides the prototype name if necessary.

No, I don't think that's an option! Localization could be ruined again... Although, only if it's LocID, then maybe...

@github-actions github-actions bot added the Merge Conflict This PR currently has conflicts that need to be addressed. label Sep 21, 2024
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the Changes: UI Can be reviewed or fixed by people who are knowledgeable with UI design label Sep 25, 2024
@Ertanic
Copy link
Contributor Author

Ertanic commented Sep 25, 2024

Yeah, that's a problem, you won't know which one is which if you don't know the recipe. Maybe add an optional translation string to the crafting menu entry that overrides the prototype name if necessary.

I left the ability to overload prototype craft names manually via fluent keys. Among other things, I added an optional ability to output suffixes.

At the request of @chavonadelal I made it possible to pull sprites from target prototypes. I didn't bother and just replaced ItemList and TextureRect by ListContainer and EntityPrototypeView. Then I will remove unused icon fields in construction prototypes.

image

image

@mirrorcult
Copy link
Contributor

extremely blessed PR

@lzk228
Copy link
Contributor

lzk228 commented Sep 25, 2024

Among other things, I added an optional ability to output suffixes.

pjb once said
image

@Ertanic
Copy link
Contributor Author

Ertanic commented Sep 26, 2024

Sneaky rider decided to brush up on unused imports.....

@Ertanic Ertanic marked this pull request as ready for review September 26, 2024 20:16
@github-actions github-actions bot added Status: Needs Review This PR requires new reviews before it can be merged. and removed Merge Conflict This PR currently has conflicts that need to be addressed. labels Sep 26, 2024
@github-actions github-actions bot added Changes: Map Can be reviewed or fixed by people who are knowledgeable with mapping. Changes: Sprites Should be reviewed or fixed by people who are knowledgeable with spriting or visual design. labels Sep 27, 2024
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the Merge Conflict This PR currently has conflicts that need to be addressed. label Sep 27, 2024
@github-actions github-actions bot removed the Merge Conflict This PR currently has conflicts that need to be addressed. label Sep 27, 2024
@Ertanic
Copy link
Contributor Author

Ertanic commented Sep 29, 2024

Due to the fact that maintainers are sabotaging the PR by their unwillingness to accept my whatever-fix of their crooked engine or to do it themselves, I have come to the conclusion that this PR is of absolutely no interest or use to them, and I am closing it.

@Ertanic Ertanic closed this Sep 29, 2024
@metalgearsloth
Copy link
Contributor

so:

  • I got randomly pinged over this PR merge-begging for it when it was only a few days old.
  • I look at the engine PR and it's bandaiding a bug and 2 maintainers ask for it to be investigated (whether it's tests or control-related).
  • Instead you tell us it's someone else's problem and refuse to fix it and we should prioritise your PR instead as someone else can fix the bug.

If you keep insisting our engine is so bad is the better solution not to investigate the root causes of issues and fix those instead of symptoms?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changes: Map Can be reviewed or fixed by people who are knowledgeable with mapping. Changes: Sprites Should be reviewed or fixed by people who are knowledgeable with spriting or visual design. Changes: UI Can be reviewed or fixed by people who are knowledgeable with UI design Status: Needs Review This PR requires new reviews before it can be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants