Xantara

Buy the Support Ticket System NOW to take advantage of the $10.00 discount! Limited time offer only. Price: $15.00 $25.00 Also updated to v1.3.2 to add in the re-open ticket feature. The demo has this update applied.

Hi guys, I totally forgot to "follow" this topic so I wasn't aware people posted stuff on here. If you still need help, post again or PM me. Someone requested an updated diff file to work with the latest rA SVN which I have now uploaded (v1.2.0). Enjoy~

Good idea. I'll have a config to enable/disable this. Thanks! It will be free and will be included as a theme in my project.

OMG, Angry Birds headgear. Astig! Oh and welcome. XP

Hmm... your config looks good. Try if these questions found on this site helps you figure out the problem. Particularly,

I ported Orcao's setcashpoints version here. I think it is similar to what you wanted ...?

Hi all, I have not forgotten this. Unfortunately, however, I have been constantly flooded with school work. Because of this, I do not have a good grasp of when I will finish everything on the front page. When I am less busy, I will also create an official project page here in the forums. As for the questions asked in this thread: - This theme design will be written for Xantara's FluxCP for rAthena project [link: git / svn]. Therefore, it will not work with eAthena - just rAthena. - Yes, this theme design and the actual CP project will be free / released to the public. - The CP is already available to download. The theme design will be branched from the current repos when started. When it is finished, it will be merged into the main/trunk. - NPCs and monster spawn information don't really change much from server to server and there are resources such as RMS for this. For custom NPCs and mobs, they are usually created in the server's Wiki or forum. Including it in the CP source will, in my opinion, increase the size unnecessarily. However, when I create the project thread, I will include it in a suggestion poll and see what the community thinks. I do like your log search suggestion though. [@@Beret] - I used Photoshop to create the images. Ragnarok renders, background image, and screenshots were taken from google images. [@] Although I am not focusing on the theme design right now, please do create bug reports here when you see any - I will look into them ASAP! Thanks for everyone's comments, patience, and understanding! ~ Xantara

This is not my mod (I believe it is icescope's since there is a tag in some of the modified areas). Anyways, I prolly found this a long time ago somewhere and saved it (I don't remember). As shown on the diff, it was made for r14109 so it might be outdated. I believe it worked though when I tried it when I first got it. account_zenychange.diff

I'm not sure what you mean for the password or the use of it. But, I can make a script and/or at command to unbind an equipped item? The code currently does not support stackable items - I'm not even sure if the client can even handle it. That is, even if an item with the bound flag enabled on a stackable item, the inventory, storage, and cart storage will still think it is a regular item. I'll try to check that out when I am not busy..

Updated: 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. Please let me know if you see any more bugs! This modification will only work on rAthena SVNs. It will not work with eA, 3ceAm, etc.

Oh, thanks for letting me know! I'll make an update sometime today (most likely tonight as I am currently at school til later in the evening). =)

Item colours are client-side. The account-bound items are able to have a different colour than normal items because official servers already have account-bound items. Thus, the client already handles such functionality (but only for that specific colour, afaik).

File Name: Account Bound Items File Submitter: Xantara File Submitted: 16 Sep 2012 File Category: Source Modifications Content Author: Xantara, Zephyrus, RO 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 At Commands Documentations 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. Click here to download this file

No, they don't drop - it keeps the same behavior as a normal non-modified @dropall.

I'm not sure what you mean by "original idea". But, the values in the DropRates array should match with whatever you put in svn/conf/battle/drops.conf For example, if you used the following settings in your (SVN) drops.conf: // The rate at which cards are dropped // Cards drop at 25x and Boss cards drop at 5x item_rate_card: 2500 item_rate_card_boss: 500 Then you would do the same in the (CP) servers.php: // The rate at which cards are dropped 'Card' => 2500, 'CardBoss' => 500, This will allow your CP to show the same rates as if you did @mobinfo in-game. It currently does not support Renewal Drop (RENEWAL_DROP in svn/src/config/renewal.h) yet. EDIT: Should be fixed in r1147 / 717fea7285

Hmm.. Yea, I had a feeling that was it. I don't know why mine doesn't complain tho =s Trying to figure out if there is a way to do operations (>, =, <) on atk:matk because of the delimiter. I might have to scrap that from the search otherwise =( I'll also have to update elv. But that has a delimiter now too! Meh, lol. Anyways, I'll commit a fix for this soon - might not be today tho but it is on my TODO list. Thanks for posting this!

It doesn't. I wonder why I can't reproduce. Please check your cp/data/logs/mysql/errors/ and cp/data/logs/errors/exceptions/ for any error print outs. Also set 'DebugMode' to true in cp/config/applications.php and $showExceptions to true in cp/config/error.php.

How about using TeamViewer instead? Anyways, I've updated the code: r1146 / 2ad4a01569. Please update and see if that fixes things.

Ah, it's the CP code. It seems like rAthena doesn't read item_db anymore when renewal is updated (since r16523) causing a conflict with the temporary tables. I'll commit a fix soon. Thanks! =) EDIT: Well, its true that the code doesn't need to read item_db anymore for renewal anymore.. But that doesn't seem like the solution for this problem since I can't reproduce your error with the current code...

Does your user have 'replace' and 'insert' permissions for the item_db_re table?

File Name: @dropall Modification & @dropalltab File Submitter: Xantara File Submitted: 02 Sep 2012 File Category: Source Modifications Content Author: Xantara, MouseJstr Information The modification on @dropall allows the user to specify what item type should be dropped. It still retains the ability to drop all items at once. The new atcommand, @dropalltab, allows the user to drop all items in a specific inventory tab. The user may choose to drop all items in all tabs (similar to the default behavior of @dropall). Tested on rAthena revision 16738. Syntax @dropall {item type} @dropalltab {tab number} Documentation Credits Created by @Xantara Requested by @Peopleperson49 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. Click here to download this file

It uses a packet that was previously marked as Unknown (see clif.c changes). After searching, it seems like iRO already has account-bounded items (for cash shop items). I'm not sure if the packet he used is the same but it does change the color (without taking a slot). I've uploaded a diff to this post. However, it is not finished - better command naming not applied, guild storage has bound column but shouldn't, and at commands aren't included. I applied some bug fixes already but would prolly need a check for mailbox (as I don't see any in *Amod) [system]_item_bound.diff

What is it? The code was taken from *Amod (but tweaked to work with rA and fixed a few bugs). 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. What does it include? - Item coloration to distinguish bounded items and non-bounded ones (see screenshot below) - 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.