inventory API is confusing when a window is open

The rules for when you can and cannot use bot.inventory while another window is open are confusing and undocumented. This is very not obvious and error prone. Make it so that accessing inventory ‘just works’ even while interacting with other open windows.

[TheDudeFromCI]

It would be easy to fix that by adding a wrapper for the inventory. If a window is open, it would read/write to that window. If the window is closed, it would read/write to bot.inventory.

Just make the editing of bot.inventory directly would be depreciated.

[u9g]

Thinking about the process further, it might also be possible to convert the existing API to getters and settings without breaking anything.

For example, rename bot.inventory.slots to bot.inventory._slots and then create a custom getter and setter function for bot.inventory.slots that would return _slots when not in a window, and would return the respective section of the currentWindow’s inventory slots if a window is open.

This would not break any existing API but should fix some of the issues.

This would be done to all of the inventory API, of course. Not just slots.

Is this still the ideal idea?