modifying screens versus menus
Screens operate only on the client while menus run on both sides, requiring full menu replacement when changing slot counts.
- Listening to the screen open event allows changing the client screen while still using the vanilla menu to communicate with the server
- Screens exist solely on the client, whereas menus must exist on both client and server sides
- Menu data typically consists of the backing container and potentially integers
- When modifying slot counts or allowing item interactions, replacing the entire menu is required rather than just swapping the screen


