[Double Cross 3rd] Sheet update: typo fixes, new consumables & vehicle sections

[CodeNameLay]

Submission Checklist

Warning

Submission Checklist
Failure to complete this checklist in its entirety will result in your Pull Request being dismissed. Deleting parts of this template (except the new sheet section for existing sheets) counts as failure to complete it. If you have any questions, please feel free to create an issue.

Note

Draft Pull Requests
If you are unclear about any of the rules regarding the creation of character sheets, or need assistance from the Roll20 team, please feel free to create a Draft PR and request feedback. We'd much rather provide assistance than reject a PR.

Pull Request Title

Please format your pull request in the following way: [Sheet Name] Change Type: Description. For example: [D&D5e] New Feature: Adding dragons to dungeons.

• The pull request title clearly contains the name of the sheet I am editing.
• The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).

Pull Request Content

• The pull request makes changes to files in only one sub-folder.
• The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)
• The pull request does not, without express prior permission from affected parties, include any material that could be considered to infringe on a Publisher's intellectual property rights, such as logos, images, rules text or other rules content.

Changes

This update improves the Double Cross 3rd Edition character sheet with several fixes and new features:

• Fixed typos and adjusted terminology
• Corrected layout and display inconsistencies
• Added a new “Consumables” (常備化) section for easier tracking
• Added a “Vehicle” category with new input fields
• Fixed multiple minor bugs and inconsistencies

All changes have been tested locally in Roll20 sandbox and verified to display correctly.

This is an update to the existing DoubleCross3rd sheet, not a new sheet submission.

Additionally, I would like to update the translations in translations/en.json and translations/ko.json to match the latest changes in the sheet.
Since the Pull Request guideline mentions that direct modification to the translations folder is not allowed, I would like to ask for clarification on the proper process for submitting translation updates.

[roll20deploy]

Character Sheet Info Roll20 Internal Use only.

[BronsonHall]

Hey @CodeNameLay

As this is an official publisher sheet owned and supported by F.E.A.R., we're going to have to request their approval on any changes to be made to this sheet. If you already have approval from them, please let us know so we can verify, but otherwise we're going to reach out w/ your summary of improvements for their review. We'll keep you updated!

As for translations, that's handled through crowdin rather than this repo - this may be a useful article. In regards specifically to the changes you're making here to the base translation.json, any new terms will appear, ready for translation on crowdin shortly after this PR is merged, defaulted to whatever translation is in the translation.json. You'll be able to add translations there, which will thereafter make their way to the two-letter files in this repo through an automated process.

If/when this PR is merged, if you have any questions on the crowdin translation process or don't see the new terms appear, don't hesitate to reach out to us!

[CodeNameLay]

Thank you for the update!

I have not previously obtained approval from F.E.A.R.
I was not aware that approval was required before submitting updates.
Therefore, I would greatly appreciate it if you could request their review on my behalf.

Thank you also for the information regarding translations.
I understand that Crowdin is the correct place to submit translation updates,
and I will follow that process going forward.

Please let me know if there is anything further I should provide.
Thanks again for your support!