Hello and greetings to all GMs after the recent patch.
I would like to propose a feature or an NPC for players to lock items that cannot be stored in the storage.
Reason?
Many times during gameplay (especially in maps with dense monster populations), I use the storage and, if I'm not quick enough, end up dying because I use the @storeall command. Similarly, when farming heavy items like Dim Weapons and returning, using @storeall requires me to search for necessary items to carry despite not wanting to store them. I know the simplest solution is to find and put those items back into my inventory, but there are cases where players don't have enough time to do so. Therefore, I think simplifying this process by creating an NPC to handle items in the inventory (ID items) or a feature to lock a certain hotkey slot would be beneficial.
Idea?
Initially, I thought about handling items I don't want to store by putting them on a hotkey and then locking that slot, so they wouldn't be counted when using @storeall. However, I felt there were many drawbacks as it directly affects the default game interface, and sometimes players need to use those hotkeys and would have to rearrange them.
So, I think creating an NPC with the function of adding item IDs to a blacklist when putting them in storage would be more intuitive and user-friendly. There would need to be certain conditions, such as the item must not be in the storage but in the player's inventory, and the NPC would allow players to input that ID to add it to the blacklist. There would also be a feature to display blacklisted items (similar to the @autolootconfig feature). The IDs would apply to entire stacks.
If the item is completely used up and no longer exists in the inventory, it will still retain its functionality until the player visits the NPC to remove that ID.
Fee?
Of course, this feature would require a fee to prevent players from using it aimlessly, only for items that are truly necessary, such as Infinite Fly Wings, Fly Wings, Kafra Card, Pot, etc., depending on the player's purpose when using the @storeall command.
This is my proposal, and I hope the GMs consider the feasibility of this issue because sometimes using a single command requires finding other items again, dragging them, alt+ right click, or forgetting and turning back to the save point. I hope there is a solution to handle them more simply and effectively.
