Amulet-Team / Amulet-Team/PyMCTranslate
"Could not find translation information for block"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 6
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 1
Description
as far as I can tell I'm doing everything correctly, I just get constant errors though.
WARNING - Could not find translation information for block minecraft:stone from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message
WARNING - Could not find translation information for block minecraft:sandstone from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message
WARNING - Could not find translation information for block minecraft:dirt from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message
WARNING - Could not find translation information for block minecraft:sand from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message
WARNING - Could not find translation information for block minecraft:water from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message
WARNING - Could not find translation information for block minecraft:oak_door from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message
WARNING - Could not find translation information for block minecraft:log[axis="y",material="oak"] from universal in PyMCTranslate.Version(java, (1, 20, 4)). If this is not a vanilla block ignore this message```
examples of my block definitions:
```these definitions work (but still give that warning)
Block("minecraft", "stone")
Block("minecraft", "grass_block", {"snowy": StringTag("true")})
these do NOT work (no block is placed in the world)
Block.from_string_blockstate("minecraft:fence_gate[material=\"oak\"]") (or Block("minecraft", "fence_gate", {"material": StringTag("oak")})```
no clue, at all.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warnings with PyMCTranslate.Version(java, (1, 20, 4)) and the Block.from_string_blockstate and Block examples shown in the report. Trace how block definitions are matched to translation information, especially state properties such as material, and compare the behavior of blocks that place successfully with fence_gate. Done means the affected vanilla blocks translate without warnings and are placed correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100