* Why it's faster:
- * - The chunk is modified directly rather than through the API
- * \ Removes some overhead, and means some processing can be done async
- * - Lighting updates are performed on the chunk level rather than for every block
- * \ e.g., A blob of stone: only the visible blocks need to have the lighting calculated
- * - Block changes are sent with a chunk packet
- * \ A chunk packet is generally quicker to create and smaller for large world edits
- * - No physics updates
- * \ Physics updates are slow, and are usually performed on each block
- * - Block data shortcuts
- * \ Some known blocks don't need to have the data set or accessed (e.g., air is never going to have data)
- * - Remove redundant extents
- * \ Up to 11 layers of extents can be removed
- * - History bypassing
- * \ FastMode bypasses history and means blocks in the world don't need to be checked and recorded
+ *
The chunk is modified directly rather than through the API
+ * - Removes some overhead, and means some processing can be done async
+ *
Lighting updates are performed on the chunk level rather than for every block
+ * - e.g., A blob of stone: only the visible blocks need to have the lighting calculated
+ *
Block changes are sent with a chunk packet
+ * - A chunk packet is generally quicker to create and smaller for large world edits
+ *
No physics updates
+ * - Physics updates are slow, and are usually performed on each block
+ *
Block data shortcuts
+ * - Some known blocks don't need to have the data set or accessed (e.g., air is never going to have data)
+ *
Remove redundant extents
+ * - Up to 11 layers of extents can be removed
+ *
History bypassing
+ * - FastMode bypasses history and means blocks in the world don't need to be checked and recorded
*/
public class Fawe {