Carpet

What's new in Carpet 1.4.144:

• support for Minecraft 24w21a

Scarpet changes:

• chunk loading API is still broken
• scarpet shapes are broken now too.

What's new in Carpet 1.4.143:

• support for Minecraft 24w20a

scarpet changes:

• temporarily (hopefully) disabled functions of relight and reset_chunk since it cannot be easily adapted to the new API. Same goes for chunk_generated and chunk_loaded events, which may come back in a different form, supported by the new chunk API

What's new in Carpet 1.4.142:

• support for Minecraft 24w18a

What's the traitor llama in Carpet 1.4.141:

• Fixed issue with carpet clients rules desynced. blame @altrisi

What's new in Carpet 1.4.140:

• support for Minecraft 1.20.5

What's new in Carpet 1.4.139:

• support for Minecraft 1.20.5 pre release 2

What's new in Carpet 1.4.138:

• support for Minecraft 1.20.5-pre1

What's new in Carpet 1.4.137:

• support for Minecraft 24w13a
• runs on Java 21

What's new in Carpet 1.4.136:

• support for Minecraft 24w13a

What's new in Carpet 1.4.135:

• support for Minecraft 24w12a

What's new in Carpet 1.4.134:

• supports Minecraft 24w09a, 24w10a and 24w11a
• adjusted stackableShulkerBoxes rule to work with the new item format. It should be now easier to stack them (they should just behave like normal stackable items), but you try to save an overstacked item (with the rule turned off) the chunk will currently crash

scarpet changes:

• changes to how item arguments are interpreted and returned throught the API.

Significant changes to the format of the items nbt affects how items are handled in scarpet. The format doesn't change, so items are still represented as a triple of [item_id, count, tag], but now the tag does not represent the extra data that the item had associated with it, but the entire tag including the count, id, and all new components. When saving of items (using inventory_set for example), if the tag is provided it will override the provided id, and if the count is provided in the triple, it will override the count in the tag. For example, the following: ['stone', 1, {}] is now ['stone', 1, {id:"minecraft:stone"}] and ['diamond_pickaxe', 1, {Damage:4}] is now ['diamond_pickaxe', 1, {components:{"minecraft:damage":4},id:"minecraft:diamond_pickaxe"}]. It is now not easy to assert if the item has no data by checking if the tag is false. You need to now check if components are missing. If you worked with items before, but didn't use the tag information, your scripts should work just fine. If you used the tags, but only in their unmodified form, for instance to copy item information from one place to another, you should be fine too. If you needed to parse item information, or were creating items with custom nbt on your own, your scripts will break and need to be adjusted.

What's new in Carpet 1.4.133:

• support for Minecraft 24w06a and 24w07a

What's new in Carpet 1.4.132:

• support for Minecraft 24w05a

What's new in Carpet 1.4.131:

• support for Minecraft 24w04a
• fixed issues with incorrect loading of quasiConnectivity on startup. Blame @altrisi

What's new in Carpet 1.4.130:

• removed spawnChunksSize as vanilla does it on its own
• fixed crashes related to spawning of fake players. blame @senseiwells

scarpet changes:

• sound would now not reject unknown sounds assuming clients may have them defined. blame @ch-yx

What's new in Carpet 1.4.129:

• support for Minecraft 23w51b

What's new in Carpet 1.4.128:

• supports Minecraft 1.20.3 and 1.20.4

scarpet changes:

• query(..., 'effect', ...) and modify(..., 'effect', ...) now supports negative durations to indicate infinity duration. blame @ch-yx

What's new in Carpet 1.4.127:

• support for Minecraft 1.20.3-pre2 and pre3

What's new in Carpet 1.4.126:

• support for Minecraft 23w46a and 1.20.3-pre1

Scarpet changes:

• fast graphics leaves now show as 'fast' with draw_shape(). blame @ch-yx
• fixed screens synchronization issues with screen_property(). blame @ch-yx

What's new in Carpet 1.4.125:

• support for Minecraft 23w45a
• Heavy rework of explosions in vanilla means that behaviour of explosions under optimizedTNT may be weird, or undefined. It is possible that optimized explosions will be sunset at some point due to un-maintained code. They seem to work right now, but that's not certain.