From 313ba2f9f449507e8f452f32f578023d5de575c1 Mon Sep 17 00:00:00 2001
From: Sergey <igentuman@gmail.com>
Date: Sat, 20 Jul 2024 01:20:49 +0200
Subject: [PATCH] Update README.md

---
 src/main/java/li/cil/oc2r/api/README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/main/java/li/cil/oc2r/api/README.md b/src/main/java/li/cil/oc2r/api/README.md
index 5da3fd24..5f99cc4b 100644
--- a/src/main/java/li/cil/oc2r/api/README.md
+++ b/src/main/java/li/cil/oc2r/api/README.md
@@ -158,6 +158,7 @@ import net.minecraft.world.level.block.entity.BlockEntity;
 import net.minecraftforge.common.capabilities.Capability;
 import net.minecraftforge.common.util.LazyOptional;
 import net.minecraftforge.fml.ModList;
+import li.cil.oc2r.api.bus.device.Device;
 
 class ModBlockEntity extends BlockEntity {
     public int getMagicValue() {
@@ -199,7 +200,7 @@ class Integration {
     // existing devices. Otherwise, the devices will technically be removed and re-added every time the device bus
     // scans for device changes. This is particularly relevant when using the lifecycle methods mount(), unmount()
     // and suspend() (e.g. if we were to implement LifecycleAwareDevice on this record).
-    record ModBlockEntityDevice(ModBlockEntity blockEntity) {
+    public record ModBlockEntityDevice(ModBlockEntity blockEntity) {
         @Callback
         public int getMagicValue() {
             return blockEntity.getMagicValue();