Introducing barrier blocks for the inventory slots that are not part of the inventory #172

Closed
opened 2020-12-30 08:18:22 -05:00 by baailey · 5 comments
baailey commented 2020-12-30 08:18:22 -05:00 (Migrated from github.com)

Implementing this feature will support a more user-friendly interface for all. My thoughts are that the barriers will go here, though if you have a different item in mind, it's your decision.

Currently if an Admin, Mod etc. try to place an item in those slots, the item will just be dropped in front of you. For those who may not be aware of this, it could result in a possibly expensive item being dropped on accident when they wanted to place it in another staff members inventory.

I hope to see this introduced!

Implementing this feature will support a more user-friendly interface for all. My thoughts are that the barriers will go [here](https://i.imgur.com/5LKMhyc.png), though if you have a different item in mind, it's your decision. Currently if an Admin, Mod etc. try to place an item in those slots, the item will just be dropped in front of you. For those who may not be aware of this, it could result in a possibly expensive item being dropped on accident when they wanted to place it in another staff members inventory. I hope to see this introduced!
Aurelien30000 commented 2021-02-11 13:04:26 -05:00 (Migrated from github.com)

On a hand I agree, however, this is a feature of the plugin:

Drop items as the other player (by putting it in the unused slots in the bottom right)

You should wait for the opinion of maintainers ;)

On a hand I agree, however, this is a feature of the plugin: _Drop items as the other player (by putting it in the unused slots in the bottom right)_ You should wait for the opinion of maintainers ;)
Jikoo commented 2021-02-11 17:02:18 -05:00 (Migrated from github.com)

I do plan to add this eventually, but it will need to be done with #150 and some internal changes to allow translations to be obtained for barrier info.

Medium complexity, low priority. See you all in 2024 when I get around to this. Just kidding. I hope.

I do plan to add this eventually, but it will need to be done with #150 and some internal changes to allow translations to be obtained for barrier info. Medium complexity, low priority. <sub>See you all in 2024 when I get around to this. <sub>Just kidding. _I hope_.</sub></sub>
RoboMWM commented 2021-02-13 11:52:54 -05:00 (Migrated from github.com)

Github supports sub/superscript? ^test

hmm im dum wut r ur secrets

Edit: ah figured it'd be HTML tags just a minute after thinking about it. Meh. Better than nothing I guess.

Github supports sub/superscript? ^test hmm im dum wut r ur secrets Edit: ah figured it'd be HTML tags just a minute after thinking about it. Meh. Better than nothing I guess.
Jikoo commented 2021-02-13 11:54:55 -05:00 (Migrated from github.com)

GitHub supports some HTML, good ol' <sub> tags.

GitHub supports some HTML, good ol' \<sub\> tags.
Jikoo commented 2024-07-03 10:30:03 -04:00 (Migrated from github.com)

The drop slot is now a client-side dropper renamed to the translation key "key.drop" which is "Drop Selected Item" in en_us. Other unused slots are a white stained glass pane with no tooltip. In the future this will be configurable.

/e: Also, wow, 2024, just as predicted. I know myself too well.

The drop slot is now a client-side dropper renamed to the translation key "key.drop" which is "Drop Selected Item" in en_us. Other unused slots are a white stained glass pane with no tooltip. In the future this will be configurable. /e: Also, wow, 2024, just as predicted. I know myself too well.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: minster586/OpenInv#172
No description provided.