Jonathan Coates 1554c7b397 Always expose nbt from turtle.getItemDetail ... - Document the thread safety of DetailRegistry a little better. - Turtles now duplicate their inventory to the "previous inventory" (now called inventorySnapshot) immediately, rather than when the block is ticked. This is slightly more resource intensive, but I don't think it's so bad we need to worry. - As this snapshot is now always up-to-date, we can read it from the computer thread. Given the item is immutable, it's safe to read NBT from it. _Technically_ this is not safe under the Java memory model, but in practice I don't think we'll observe the wrong value. Closes #1306		2023-01-25 18:37:14 +00:00
..
common	Always expose nbt from turtle.getItemDetail	2023-01-25 18:37:14 +00:00
common-api	Always expose nbt from turtle.getItemDetail	2023-01-25 18:37:14 +00:00
core	Fix a few typos	2023-01-24 18:47:29 +00:00
core-api	Don't round trip values in executeMainThreadTask	2022-12-15 20:19:28 +00:00
fabric	Fix printouts crashing in item frames	2023-01-09 18:28:44 +00:00
fabric-api	Initial pass of the API breaking changes for 1.19.3 (#1232)	2022-12-03 15:02:00 +00:00
forge	Enforce version bounds for the Kotlin stdlib	2023-01-17 20:28:31 +00:00
forge-api	Resolve a few TODOs	2022-12-03 15:55:48 +00:00
lints	Add a couple of errorprone plugins	2022-11-10 08:54:09 +00:00
web	Update project paths in our utility build scripts	2022-11-10 09:12:28 +00:00
ARCHITECTURE.md	Fix some typos in ARCHITECTURE.md	2022-12-14 18:49:06 +00:00