I love this alternative backpack system for roblox but I wanted to ask a question considering I don’t do much scripting is changing the position of the slots below the screen.
I didn’t see any configuration for changing its position in the attributes and it was difficult to find it in the main script.
Major Issue: Controller Bumper Buttons Not Selecting Tools
Hey, we are currently aware of a current issue relating to not being able to select tools on a controller using the bumper buttons. A temporary fix is now available in the 6-bug-controller-bumper-buttons-not-selecting-tools branch for Satchel.
Issue Tracking
Branch with Temporary Fix
Estimated time for a permanent solution is within about a week with the release of 1.1.0. If there are any issues or problems message me or create an issue on the GitHub.
While Satchel does use the deprecated .Draggable internally, just like type safety, changing the dragging behavior to another which isn’t deprecated that high in our priority list. The current dragging system is fine now and poses no problems, rewriting or adding code to Satchel can add potentially add more bugs with little benefits.
If any issues with using the deprecated property do arise, I will definitely look to rewrite how dragging works.
With the current version of Satchel, you can’t remove the Icon module or Satchel will break. I just fixed this issue with Use Icon in ReplicatedStorage if possible so look forward to 1.1.0. Basically, what it does is if it detects Icon in ReplicatedStorage, it will use that instead and destory it’s Icon child.
Additionally, if you don’t want to wait for 1.1.0 you can just use the main branch of Satchel.
I agree, I play a game quite a bit where I have to rearrange my backpack on spawn, its very frustrating the way that property works. It drags slightly then stops, before teleporting to a random place after letting go of your mouse.
I’ve investigated the issue and found it is indeed related to the .Draggable property. Thanks for giving me information for an issue with using the deprecated property to me.
I will try my best to resolve this issue in, hopefully, the next release of Satchel.
Having documentation is something I will never rule out but as it stands now, the work needed to make documentation is very high compared to just listing them in the initial post.
I tried having documentation for my past projects but analytics showed that less than ~3% of users (who purchased the model on Creator Marketplace) actually visit and read the documentation. This accounts to less than 10 unique visitors for documentation considering how it takes hours to write and create the documentation when it can be spent on improving the module.
What do you mean by make the hotbar button always visible?
Under normal gameplay the hotbar is usually always visible. The TopBar button to toggle the inventory is only hidden when in the Roblox Menu like with other CoreGui but again you can’t click the button while in the Roblox Menu so it makes sense to hid the unclickable button.
Having documentation actually drives more people to use your package. I noticed that after documenting every API and writing a tutorial on each subject gave my framework more impressions, people also asked for help less and less as I added more.
When your character dies or resets in Satchel, all your backpack items are kept and the positions in the hotbar remain the same. This is the same behavior for the default backpack.