About This File
Information
This system would allow (non-stackable, non-pet-egg) items to be bounded onto a player's account. This means that the bounded items cannot be traded, dropped, auctioned, nor mailed. But, they can be storaged so that it can be shared among the characters of that account.
Features:
- Item coloration to distinguish bounded items and non-bounded ones (see screenshot)
- Script commands (getitembound, getitembound2, equipisbounded) to create and check for bounded items
- At commands (@itembound, @itembound2) to create bounded items
- New group permission (can_trade_bounded) to allow the group to distribute these bounded items if enabled (mostly just for High GMs / Admins)
- Changes to the SQL files to track bounded items. This would effect cart, inventory, and storage databases.
Tested on rAthena revision 17294 (using v1.5.1).
Script Command Documentations
*getitembound <item id>,<amount>{,<account ID>};
*getitembound "<item name>",<amount>{,<account ID>};
This command will give an amount of specified items to the invoking character. If an optional account ID is specified, and the target character is currently online, items will be created in their inventory instead. If they are not online, nothing will happen.
It works essentially the same as 'getitem', except that items created using this command will bound the item to the player's account. They will not be able to trade, sell, drop, nor auction the item.
*getitembound2 <item id>,<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<account ID>};
*getitembound2 "<item name>",<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<account ID>};
This command will give an amount of specified items to the invoking character. If an optional account ID is specified, and the target character is currently online, items will be created in their inventory instead. If they are not online, nothing will happen.
It works essentially the same as 'getitem2', except that items created using this command will bound the item to the player's account. They will not be able to trade, sell, drop, nor auction the item.
*equipisbounded <equipment slots>;
This command will check if the item in the specified equipment slot is bounded to the player's account or not. It will return 1 if bounded, 0 otherwise. For a list of equipment slots see 'getequipid'.
At Commands Documentations
@itembound <item name/ID> {<amount>}
Creates the specified item and bounds it to the account.
If an amount is given for @itembound, that number will be created.
@itembound2 <item name/ID> <quantity> <identify_flag> <refine> <attribute> <card1> <card2> <card3> <card4>
Creates an item with the given parameters (the 'cards' can be any item) and bounds it to the account.
identify_flag: 0 = unidentified, 1 = identified
attribute: 0 = not broken, 1 = broken
Known Issues
- When moving a bounded item to storage, item colouration is gone. However, re-opening the storage or re-logging will fix this issue.1
- When moving a bounded item to the cart inventory, item colouration is gone. However, re-logging will fix this issue.1
1 If you are able to find these packets (ie. PACKET_ZC_ADD_ITEM_TO_STORE3 and/or PACKET_ZC_ADD_ITEM_TO_CART3), please let me know!
Credits
Created by @Xantara
Popularized by Zephyrus
Idea by Ragnarok Online
License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Like my work?
Rate/vote this download
Rep up my support topic post
Do not mirror without my consent.
What's New in Version 1.1.1 See changelog
Released
- v1.0.3 Initial Release
- v1.1.0 Fixed/changed msg_conf numbers.
- v1.1.1 Fixed itembound2 bug where it allowed the creation of stackable items or pet egg/equipment.