-
-
Notifications
You must be signed in to change notification settings - Fork 416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extra Inventory Slots #652
Comments
This is actually proven to work already, it’s a feature in many other hacked clients called Xcarry. I don’t use wurst much but I recommend checking to see if they already have it since it’s a common feature. |
its been a while and i didnt find it on the wiki. i hope i can draw a bit more attention to this great feature with this message xD |
This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks. Issues should be closed if:
|
Still relevant. |
This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks. Issues should be closed if:
|
Still relevant. |
This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks. Issues should be closed if:
|
This is a pretty standard feature in hacked clients, wurst rly should have built in support |
If you turn on touchscreen mode and then drag items into your 4x4 crafting grid, then click out of your inventory instead of using the esc/e key the items will stay in the crafting grid and can be used as four extra inventory slots. Just wondering if this could be exploited with code.
The text was updated successfully, but these errors were encountered: