Leaderboard

Just because rAthena stands for "Renewal" not a lot of PEOPLE LIKE RENEWAL FEATURES. Maybe more then half the community might not like Renewal features but love rAthena's emulator because they've been updating a lot and we can use pre-renewal or renewal just by commenting something out. You're simply discriminating against people who enjoy pre-renewal. It's like if we were to make a Forum Board or an emulator only for the Asian race and the African Americans, Caucasians, and other race's can't use it or can't be associated (This is what you're practically, in a nutshell, trying to suggest or mention). rAthena is an OPEN source, and OPEN board with open Advertisements (of course, simply following their rules). You cannot simply block out everyone else just because they love Pre-Renewal rather than Renewal.

File Name: NPC Auction System File Submitter: Taeko File Submitted: 11 May 2012 File Category: NPC Sprites Content Author: Taeko, RO Staff Hi! On the server where I played was not used at all the Auction System, knowing it was an excellent system to encourage a bit that I wanted to create a NPC to make it more appealing. The idea is inspired board game WAKFU as this board can sell and buy it there, it is notable that with a good script can make the sprite can not only be used for the auction system but to other systems as broadcasting or why not leave messages for the players when they are off, creativity and depends entirely on the scripter. This sprite contains material from the official NPC only did the board. All rights are reserved to them, hope you like and can enjoy it ^ ^ Thanks to Shiro, Tenedor and FuwaRO already closed: P Click here to download this file

File Name: Fallen Season Prontera by Olrox File Submitter: Olrox File Submitted: 29 Dec 2011 File Category: Maps & Textures Video: Content Author: Olrox < -- For More Screenshots, Videos, and Support of this Map Click Me --> A fallen season prontera made with this real fallen season leaves ... that your users will love for sure! This wonderfull prontera is just your right choice for the autumn season in your time zone. This is the first and unique release that recreates the autumn season so nearly, by adding colorfull trees from red, orange, to yellow, by using mapple trees. Any question please refer to the support topic. File attaches is in 7z (7-zip) pack, that you can extract with 7-zip or winrar. Click here to download this file

steps by steps how to add maps in existing map_cache.dat. thanks for helping me. i needed it for my server.

party.c: if (p && p->party.item&2 && (first_charid || !(battle_config.party_share_type&1))) Change to: if (p && ((p->party.item&2 && (first_charid || !(battle_config.party_share_type&1))) || map[sd->bl.m].name == "map"))

- script no_reins2 -1,{ OnPCLoadMapEvent: if (strcharinfo(3) == prontera && ismounting() ) { setmounting(); } } prontera mapflag loadevent That should work now. I found the documentation for it. http://rathena.org/wiki/MountingNPCHandle

Hi mnjfx, I would recommend turning error reporting on by editing '/config/error.php', and also turning on debug in '/config/application.php'. Then try to reset again, see what error it states when you try to do it.

Awsome Taeko! Nice WORK! Regards

Absolutely gorgeous sprite!

@manabeast : 1) You can't really have both, well, you can, but you'd need a specific decarder npc that will only decard the 1st slot cards (because the generic decarder npc takes out the cards from all the slots in the item) otherwise you would have a bug where people would enchant their equip, decard, and then a new slot would appear (the slot where the enchantment was), as if they decarded the enchantment as well. EDIT: I believe the best way to do this, is by editing the src/map/script.c in the function "successremovecards" and "failedremovecards" EDIT: This change will only work if you use cards only in the first slot of armor-type equipments (otherwise you can't use the enchantment system at all). EDIT: I tried doing this for you, but i'm not sure it may work, edit your script.c : Find (inside "successremovecards" AND "failedremovecards") if(itemdb_isspecial(sd->status.inventory[i].card[0])) return 0; for( c = sd->inventory_data[i]->slot - 1; c >= 0; --c ) { if( sd->status.inventory[i].card[c] && itemdb_type(sd->status.inventory[i].card[c]) == IT_CARD ) {// extract this card from the item Replace with : if(itemdb_isspecial(sd->status.inventory[i].card[0])) return 0; for( c = ( sd->inventory_data[i]->type == IT_WEAPON ? (sd->inventory_data[i]->slot - 1) : 0 ); c >= 0; --c ) { if( sd->status.inventory[i].card[c] && itemdb_type(sd->status.inventory[i].card[c]) == IT_CARD ) {// extract this card from the item compile, then try it out 2) You can make the npc not destroy your item if you simply take out or comment the delitem command from the failure attempts : Search preferably for the line "// Fail" // Fail if (rand(0,100) > (90 - (10*.@slot_num))) { specialeffect2 306; mes "["+strnpcinfo(1)+"]"; mes "Wooops! I'm sorry, but it broke. There's nothing I can do about it anymore."; set Zeny, Zeny - .@zeny_cost; delitem .@itemid,1; close; } with // Fail if (rand(0,100) > (90 - (10*.@slot_num))) { specialeffect2 306; mes "["+strnpcinfo(1)+"]"; mes "Wooops! I'm sorry, but it failed. There's nothing I can do about it."; // <---- Changed text set Zeny, Zeny - .@zeny_cost; // delitem .@itemid,1; <---- Commented or Remove this line close; } Note : Make sure you make that replacement in the three type of enchantments. Note : The three types of failures are different, make sure you only edit the needed lines (the delitem command and the text). 3) the lack of sprite in the item sounds like something from the txt file in data folder "idnum2itemresnametable.txt" make sure you have added correctly the korean sprites for the enchantment items anywhere inside that file : 25000#·¹µåºí·¯µå# 25001#·¹µåºí·¯µå# 25002#À©µå¿Àºê¹öµÀ¾î# 25003#À©µå¿Àºê¹öµÀ¾î# 25004#À©µå¿Àºê¹öµÀ¾î# 25005#¾î¸Ó´ÏÀǾǸù# 25006#¾î¸Ó´ÏÀǾǸù# 25007#¾î¸Ó´ÏÀǾǸù# 25008#¿ëÀǺ¸Áö_È«# 25009#¿ëÀǺ¸Áö_È«# 25010#¿ëÀǺ¸Áö_Ȳ# 25011#¿ëÀǺ¸Áö_Ȳ# 25012#¿ëÀǺ¸Áö_Ȳ# 25013#ÆĶõ»öº¸¼®# 25014#ºÓÀº»öº¸¼®# 25015#ºÓÀº»öº¸¼®# 25016#Ãê·Ï»öº¸¼®# 25017#Ãê·Ï»öº¸¼®# 25018#婸®½ºå»ºí·Ç# 25019#婸®½ºå»ºí·Ç# 25020#婸®½ºå»ºí·Ç# 25021#¿»·î¿ì¶ÓÀìºê# 25022#¿»·î¿ì¶ÓÀìºê# 25023#¾î¸Ó´ÏÀǾǸù# 25024#¾î¸Ó´ÏÀǾǸù# 25025#¾î¸Ó´ÏÀǾǸù# 25026#¿ëÀǺ¸Áö_û# 25027#¿ëÀǺ¸Áö_û# 25028#¿ëÀǺ¸Áö_û# 25029#ºÐÈ«»öº¸¼®# 25030#ºÐÈ«»öº¸¼®# 25031#Çϴûöº¸¼®# 25032#Çϴûöº¸¼®# 25033#º¸¶Ó»öº¸¼®# 25034#º¸¶Ó»öº¸¼®# 25035#°ëºÓÀºº¸¼®# 25036#°ëºÓÀºº¸¼®# 25037#°ëºÓÀºº¸¼®# 25038#婸®½ºå»ºí·Ç# 25039#婸®½ºå»ºí·Ç# 25040#婸®½ºå»ºí·Ç# 25041#¿»·î¿ì¶ÓÀìºê# 25042#¿»·î¿ì¶ÓÀìºê# 25043#¾î¸Ó´ÏÀǾǸù# 25044#¾î¸Ó´ÏÀǾǸù# 25045#¾î¸Ó´ÏÀǾǸù# 25046#¿ëÀǺ¸Áö_û# 25047#¿ëÀǺ¸Áö_û# 25048#¿ëÀǺ¸Áö_û# 25049#¿ëÀǺ¸Áö_È«# 25050#¿ëÀǺ¸Áö_È«# 25051#¿ëÀǺ¸Áö_È«# 25052#Çϴûöº¸¼®# 25053#Çϴûöº¸¼®# 25054#º¸¶Ó»öº¸¼®# 25055#º¸¶Ó»öº¸¼®# 25056#Ãê·Ï»öº¸¼®# 25057#Ãê·Ï»öº¸¼®# 25058#Ãê·Ï»öº¸¼®# 25059#¿»·î¿ì¶ÓÀìºê# 25060#¿»·î¿ì¶ÓÀìºê# 25061#¿»·î¿ì¶ÓÀìºê# 25062#婸®½ºå»ºí·Ç# 25063#婸®½ºå»ºí·Ç# 25064#婸®½ºå»ºí·Ç# 25065#¾î¸Ó´ÏÀǾǸù# 25066#¾î¸Ó´ÏÀǾǸù# 25067#¾î¸Ó´ÏÀǾǸù# 25068#¿ëÀǺ¸Áö_û# 25069#¿ëÀǺ¸Áö_û# 25070#¿ëÀǺ¸Áö_û# 25071#¿ëÀǺ¸Áö_Ȳ# 25072#¿ëÀǺ¸Áö_Ȳ# 25073#¿ëÀǺ¸Áö_Ȳ# 25074#¿ëÀǺ¸Áö_Ȳ# 25075#¿ëÀǺ¸Áö_Ȳ# 25076#¿ëÀǺ¸Áö_³ì# 25077#¿ëÀǺ¸Áö_³ì# 25078#¿ëÀǺ¸Áö_³ì# 25079#Ãê·Ï»öº¸¼®# 25080#Ãê·Ï»öº¸¼®# 25081#·¹µåºí·¯µå# 25082#·¹µåºí·¯µå# 25083#·¹µåºí·¯µå# 25084#À©µå¿Àºê¹öµÀ¾î# 25085#婸®½ºå»ºí·Ç# 25086#婸®½ºå»ºí·Ç# 25087#¾î¸Ó´ÏÀǾǸù# 25088#¾î¸Ó´ÏÀǾǸù# 25089#¾î¸Ó´ÏÀǾǸù# 25090#¿ëÀǺ¸Áö_È«# 25091#¿ëÀǺ¸Áö_û# 25092#¿ëÀǺ¸Áö_û# 25093#¿ëÀǺ¸Áö_û# 25094#Ȳ±Ý# 25095#Ȳ±Ý# 25096#Ȳ±Ý# 25097#ÇÁ·¹ÀÓÇÏÆ®# 25098#ÇÁ·¹ÀÓÇÏÆ®# 25099#±×·¹ÀìÆ®³×ÀìÃÄ# 25100#±×·¹ÀìÆ®³×ÀìÃÄ# 25101#Ãê·Ï»öº¸¼®# 25102#Ãê·Ï»öº¸¼®# 25103#婸®½ºå»ºí·Ç# 25104#婸®½ºå»ºí·Ç# 25105#À©µå¿Àºê¹öµÀ¾î# 25106#À©µå¿Àºê¹öµÀ¾î# 25107#¿»·î¿ì¶ÓÀìºê# 25108#¾î¸Ó´ÏÀǾǸù# 25109#¾î¸Ó´ÏÀǾǸù# 25110#¾î¸Ó´ÏÀǾǸù# 25111#¿ëÀǺ¸Áö_È«# 25112#¿ëÀǺ¸Áö_û# 25113#¿ëÀǺ¸Áö_û# 25114#ºÐÈ«»öº¸¼®# 25115#¾È½Ç¶Ó# 25116#¾È½Ç¶Ó# 25117#¾È½Ç¶Ó# 25118#°ëºÓÀºº¸¼®# 25119#°ëºÓÀºº¸¼®# 25120#°ëºÓÀºº¸¼®# 25121#¾È½Ç¶Ó# 25122#¾È½Ç¶Ó# 25123#¾È½Ç¶Ó# 25124#ÆĶõ»öº¸¼®# 25125#ºÓÀº»öº¸¼®# 25126#ºÓÀº»öº¸¼®# 25127#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25128#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25129#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25130#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25131#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25132#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25133#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25134#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25135#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25136#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25137#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25138#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25139#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25140#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25141#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25142#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25143#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25144#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25145#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25146#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 25147#°å´ëÇѺê¶ÓµÐ¿òÁ¶°¢# 30000#ºê¶ÓµÐ¿òÆÄÆí# 4) The lack of power stones might be associated to what item ID you set to be the power stone in your server, it simply checks for item ID 30000, if you didn't set the item to that number, it won't check properly. If that's not the case, i'm honestly not sure on what's the problem, that's all I can think of. @sizenine 1) I guess you can replace the following code : for( set .@i,1; .@i <= 6; set .@i,.@i+1 ) { if ((.@i == 3) && (getiteminfo(getequipid(3),5) == 32) && (getequipisequiped(.@i))) { // Only catch shields set .@menu$, .@menu$ + .@position$[.@i] + "-" + "[" + getequipname(.@i) + "]"; set .@arr[.@j], .@i; set .@j, .@j + 1; set .@menu$, .@menu$ + ":"; } if(getequipisequiped(.@i) && (.@i != 4) && (.@i != 3)) { set .@menu$, .@menu$ + .@position$[.@i] + "-" + "[" + getequipname(.@i) + "]"; set .@arr[.@j], .@i; set .@j, .@j + 1; set .@menu$, .@menu$ + ":"; } } with // Sets array for blacklist elements setarray .@blacklist[0], 1501 ; for( set .@i,1; .@i <= 6; set .@i,.@i+1 ) { if ((.@i == 3) && (getiteminfo(getequipid(3),5) == 32) && (getequipisequiped(.@i))) { // Only catch shields set .@menu$, .@menu$ + .@position$[.@i] + "-" + "[" + getequipname(.@i) + "]"; set .@arr[.@j], .@i; set .@j, .@j + 1; set .@menu$, .@menu$ + ":"; } for (set .@k, 0; .@k < getarraysize(.@blacklist); set .@k, .@k + 1 ) { if (getequipid(.@i) == .@blacklist[.@i]) { set .@blacklisteq, 1; break; } } if(getequipisequiped(.@i) && (.@i != 4) && (.@i != 3) && (!.@blacklisteq)) { set .@menu$, .@menu$ + .@position$[.@i] + "-" + "[" + getequipname(.@i) + "]"; set .@arr[.@j], .@i; set .@j, .@j + 1; set .@menu$, .@menu$ + ":"; } set .@blacklisteq, 0; } then you can replace the numbers in the array with the item IDs you want, that is for example : If you wanted to set the blackist array for item IDs 1501, 1502 and 1503 : replace setarray .@blacklist[0], 1501 ; with setarray .@blacklist[0], 1501, 1502, 1503 ; and so on. Just a notice that this is a really simple fix to the script, meaning the blacklisted items simply won't show in the equipment list. But if somehow a player manages to switch their equipments while talking to the NPC (through a hack or 3rd party prog), they could get through this fix.. if you want to prevent that, you could add something like that : Replace : if (countitem(.@itemid) > 1) { mes "["+strnpcinfo(1)+"]"; mes "Ah, looks like you have more than one of the same item in your inventory, I'm sorry but you must store them first before proceeding."; close; } mes "["+strnpcinfo(1)+"]"; with if (countitem(.@itemid) > 1) { mes "["+strnpcinfo(1)+"]"; mes "Ah, looks like you have more than one of the same item in your inventory, I'm sorry but you must store them first before proceeding."; close; } for (set .@k, 0; .@k < getarraysize(.@blacklist); set .@k, .@k + 1 ) { if (getequipid(.@i) == .@blacklist[.@i]) { mes "["+strnpcinfo(1)+"]"; mes "Sorry but the equipment you are using cannot be enchanted."; close; } } mes "["+strnpcinfo(1)+"]"; you can add both changes, or just the second change, if you add both, the equipment won't show in the list of equipments to be enchanted. if you add only the second, it will show in the list but you won't be able to enchant it in the end (just make sure you define the blacklist array somewhere if you add only second change). I recommend you add both, though. Note: Untested, but i believe it should work.

Guardian Hunter (warning: bad english) This is a small minigame I made where you can play forever until you die or relog. SQL TOP 10 List included. The goal is to stay alive as long as you can. Every round one guardian more will be spawned where it gets harder and harder. For each kill you get a amount of zeny. You can set the maps, monster ids and the amount of zeny. The script is dynamic + spawns the monster ids randomly but with the correct amount for each round. Have Fun with it Files guardian_hunter_1.0.0.txt guardian_hunter_1.0.1.txt guardian_hunter_1.1.1.txt guardian_hunter_1.1.2.txt Changelogs 1.0.0 Release 1.0.1 Fixed first monster spawn 1.1.1 Added '@currentroom$' into monsterspawn to prevent spawning mobs outside guardian rooms after fast relog 1.1.1 Added 'x Guardians left' notification after every kill 1.1.1 Changed '(0/1)' & '(1/1)' into '(Free)' & '(Full)' 1.1.2 Added autowarp after death Features Configurable maps, monster ids, zeny reward Everything is dynamic SQL TOP 10 List How can you help me ? Give me feedback Report bugs Tell me if you like it tr0n