I will definitely look towards seeing how to change the keybinds for a later release. As it stands Rojo, the software we use to sync scripts, doesn’t support syncing enum attributes such as Font, BorderMode, KeyCode, and more.
Until Rojo support enum attributes, I will have to hold off of adding support for them.
Is there a way to easily disable this backpack? My game uses :SetCoreGuiEnabled and I can’t find an equivalent function in Satchel to toggle it’s usage on and off.
Thanks!
Satchel is an open-source project which receives no direct compensation or monetization with its open free-to-use modal. Satchel’s goal is to provide a high quality resource for developers to both utilize and learn from.
We are looking for contributors and maintainers for Satchel to keep it in a bug-free and robust state.
All contributions are welcome. Learn to contribute on Satchel by visiting CONTRIBUTING.md.
Systems for doing so are already available for the default backpack and should work with Satchel with moderate modifications.
Adding systems to save tools and restore them would mean adding significant code to Satchel and utilizing data stores which is out of the scope for Satchel.
For those using TextChatService and are encountering the bug where entering numbers in the chat continues to select items from the Satchel toolbar, you can add a couple of lines to mitigate (and hopefully eliminate) the problem:
Add to the beginning of SatchelScript:
local TextChatService = game:GetService("TextChatService")
local ChatInputBarConfiguration = TextChatService:FindFirstChildOfClass("ChatInputBarConfiguration")
Modify the first if statement in OnInputBegan():
...
if
input.UserInputType == Enum.UserInputType.Keyboard
and not TextBoxFocused
and not ChatInputBarConfiguration.IsFocused -- This line here!
and (WholeThingEnabled or input.KeyCode.Value == DROP_HOTKEY_VA
then
...
v1.0.0 is the first stable release of Satchel. This release refactors major portions of the code with the goal to make the code more readable and easier to contribute to. Changes include bug fixes and minor improvements.
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.