The journey to version 2.0

[scriptsengineer]

I'm starting a major refactoring for a more concise and definitive version of this asset.

Some goals for this version include:

• 🗑️Removal of the open/close logic from gdextension
  I've found that this doesn't make sense to be in this plugin, it could be something very specific to each project and it just makes this lib very rigid for changes.

• 😎More obvious names for methods and parameters
  In the current version, we have many parameters and methods that are very specific to understand, the idea is to make it easy to read, something close to what the class would be if it were part of Godot itself.

• ✂️Removal of interaction classes
  I believe that they can be moved to the example and only used as a source of knowledge, the interaction classes today can be very simple for several projects that want to take advantage of more features involved, but still use the core inventory system.

• ↔️ Move scripts from the editor to gdextension
  Editor scripts can be placed inside gdextension improving its performance and ensuring that the whole heart of the plugin is in a single gdextension file.

• 📖Add minimal tutorials
  The lack of tutorials today is one of the biggest problems, the goal of making the asset learning curve easier includes adding several tutorials on how to use this asset to its full potential.

• 📋Add class reference
  With update 4.3, it is now possible to add class references to gdextension. This is already very incredible, as we can describe how to use methods and classes and even include mini tutorials in the documentation that appears inside godot.

• 📋Serialize/Deserialize Methods
  Add option to save datas

---

Let me know what you think of these scope changes.

[TheYellowArchitect]

I think tutorials/docs/classreference are definitely needed. This plugin satisfies my needs (3D placeable items and multiplayer), but I cannot understand it completely to write my own logic for certain parts. I press ctrl to see the code of InventoryHandler or Interactor and I have a page of nothing. Even fundamental code like InventoryHandler.open_main_inventories() which does more than that - it also reveals mouse, so how can I trust that any function doesn't do more than it says?
As a result, I am not confident to use it on my project. The demo even has multiplayer and 3D placement, both features I want, but its just risky to use code I don't completely understand, nor can read (C++)

Anyway, if you are close to to finishing the code refactor, finish the refactor first, don't delay that

[scriptsengineer]

Your words sum up this necessary refactor, with all its objectives, such as class reference and complete separation between the demo and the plugin core.
My estimate is to have something ready in two weeks, at the moment I'm trying to speed up everything I can, for example the open/close issue has already been removed.

[TheYellowArchitect]

I am very happy to read this :)
Both that you understand the benefits of the refactor, and also to hear that it's not a "roadmap" but is literally being developed right now, you got this! 💪