You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/meta/style-guide.md
+33-31
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
2
title: Style Guide
3
+
description: A guide for keeping Minecraft creations consistent.
3
4
mentions:
4
5
- SirLich
5
6
- solvedDev
6
7
- MedicalJewel105
7
8
- ChibiMango
8
9
- zheaEvyline
9
10
- QuazChick
10
-
description: Officially supported Bedrock Wiki style guide for add-on creation.
11
11
---
12
12
13
-
This document will present the officially supported Bedrock Wiki style guide for add-on creation. This guide aims to promote best practices while creating add-ons and create a consistent format for everyone to follow.
13
+
This document will present the Bedrock Wiki style guide for add-on creation. This guide aims to promote best practices while creating add-ons and create a consistent format for everyone to follow.
14
14
15
15
:::tip
16
16
The style guide is a living, breathing document, which will evolve as add-on creation evolves. Please get in touch if you think something needs to be updated or changed!
@@ -24,51 +24,55 @@ The style guide is a living, breathing document, which will evolve as add-on cre
24
24
- Content folders should use consistent pluralization: Stick with names that are either all plural or all singular, don't mix and match. Example:
- All content folders `abilities`, `events`, and `quests` are consistently pluralized.
34
-
- The content folders in `events` are also consistent, as both `player` and `world` are singular.
34
+
35
+
- All content folders `abilities`, `events`, and `quests` are consistently pluralized.
36
+
- The content folders in `events` are also consistent, as both `player` and `world` are singular.
35
37
36
38
❌️ Inconsistent:
39
+
37
40
```
38
41
BP/functions/ability/ice_blast.mcfunction
39
42
BP/functions/event/players/on_death.mcfunction
40
43
BP/functions/event/world/on_initialise.mcfunction
41
44
BP/functions/quests/jungle/1.mcfunction
42
45
```
43
-
- Only `quests` content folder is pluralized while `ability`, and `event` are singular.
44
-
- Also, in the `event` folder, the `players` folder is plural while `world` is singular.
46
+
47
+
- Only `quests` content folder is pluralized while `ability`, and `event` are singular.
48
+
- Also, in the `event` folder, the `players` folder is plural while `world` is singular.
45
49
46
50
## Identifiers
47
51
48
52
Do not use identifiers that begin with a number, and especially don't use an identifier that is _only_ a number. This applies to entities, component_groups, events, and anything else that takes a `namespace:name` pair.
- do not include your namespace in any folder path or file-name
96
+
- do not include your namespace in any folder path or filename
93
97
94
98
## Sub-Indexing
95
99
@@ -273,8 +277,8 @@ Own-line comments can be used for organizational purposes but should not store l
273
277
| BDS | Bedrock Dedicated Server |
274
278
| FPV | First Person View |
275
279
| RD | Render Dragon |
276
-
| VSCode | Visual Studio Code |
277
280
| SP | Skin Pack |
281
+
| VSCode | Visual Studio Code |
278
282
279
283
## Definition Format Orders
280
284
@@ -327,5 +331,3 @@ Blocks, entities and items should follow the format order below.
327
331
328
332
PascalCase should be used with `BlockComponent` or `ItemComponent` as a suffix. As an example, `const MeltableBlockComponent = { ... }` rather than `const meltable = { ... }`.
329
333
This helps to differentiate what we're using in `registerCustomComponent` and what we're using as values elsewhere.
0 commit comments