Minecraft:angry - Inproper case use
Partner Rank: 4
Partner Team Reporting: Blockception
Verification builds: 1.17.40
Summary:
Some uses of `minecraft:angry` component use a different case type for properties, while official documentation recommends snake_case. I understand this is supported but it is better if its all snake_case for validation, tools and just usability
Impact:
- Good examples for the community to use.
- Correct working vanilla data-driven files.
Repro Steps:
Observed Results:
Expected Results:
Correct, consistent vanilla files that not only follows Minecraft readable format but also by written convention/documentation.
Screenshots/Videos attached: No
Regression Builds: N/A
Notes:
Suggested course of action:
Replace the following with vscode:
- `broadcastAnger` with `broadcast_anger`
- `broadcastRange` with `broadcast_range`
Files:
- behaviorpack/entities/bee.json
- behaviorpack/entities/wander_trader.json