Leaderboard

Open ../src/map/clif.cpp and in the function clif_parse_LoadEndAck remove: #if PACKETVER >= 20070918 clif_partyinvitationstate(sd); clif_equipcheckbox(sd); #endif #if PACKETVER >= 20141008 if( battle_config.pet_autofeed_always ){ // Always send ON or OFF if( sd->pd && battle_config.feature_pet_autofeed ){ clif_configuration( sd, CONFIG_PET_AUTOFEED, sd->pd->pet.autofeed ); }else{ clif_configuration( sd, CONFIG_PET_AUTOFEED, false ); } }else{ // Only send when enabled if( sd->pd && battle_config.feature_pet_autofeed && sd->pd->pet.autofeed ){ clif_configuration( sd, CONFIG_PET_AUTOFEED, true ); } } #endif #if PACKETVER >= 20170920 if( battle_config.homunculus_autofeed_always ){ // Always send ON or OFF if( sd->hd && battle_config.feature_homunculus_autofeed ){ clif_configuration( sd, CONFIG_HOMUNCULUS_AUTOFEED, sd->hd->homunculus.autofeed ); }else{ clif_configuration( sd, CONFIG_HOMUNCULUS_AUTOFEED, false ); } }else{ // Only send when enabled if( sd->hd && battle_config.feature_homunculus_autofeed && sd->hd->homunculus.autofeed ){ clif_configuration( sd, CONFIG_HOMUNCULUS_AUTOFEED, true ); } } #endif In the function clif_parse_LoadEndAck after: // Notify everyone that this char logged in [Skotlex]. map_foreachpc(clif_friendslist_toggle_sub, sd->status.account_id, sd->status.char_id, 1); add: #if PACKETVER >= 20070918 clif_partyinvitationstate(sd); clif_equipcheckbox(sd); #endif #if PACKETVER >= 20141008 if( battle_config.pet_autofeed_always ){ // Always send ON or OFF if( sd->pd && battle_config.feature_pet_autofeed ){ clif_configuration( sd, CONFIG_PET_AUTOFEED, sd->pd->pet.autofeed ); }else{ clif_configuration( sd, CONFIG_PET_AUTOFEED, false ); } }else{ // Only send when enabled if( sd->pd && battle_config.feature_pet_autofeed && sd->pd->pet.autofeed ){ clif_configuration( sd, CONFIG_PET_AUTOFEED, true ); } } #endif #if PACKETVER >= 20170920 if( battle_config.homunculus_autofeed_always ){ // Always send ON or OFF if( sd->hd && battle_config.feature_homunculus_autofeed ){ clif_configuration( sd, CONFIG_HOMUNCULUS_AUTOFEED, sd->hd->homunculus.autofeed ); }else{ clif_configuration( sd, CONFIG_HOMUNCULUS_AUTOFEED, false ); } }else{ // Only send when enabled if( sd->hd && battle_config.feature_homunculus_autofeed && sd->hd->homunculus.autofeed ){ clif_configuration( sd, CONFIG_HOMUNCULUS_AUTOFEED, true ); } } #endif

All headgear official bRO, cRO, euRO, fRO, idRO, iRO, jRO mysgRO, twRO, tRO Update November 2022 Headgear November 2022.7z Iclude list and miss headgear

Just a simple modification to enable/disable Discount or Overcharge on specified NPC Shop. Maybe the idea was brought from Shop System and my old commit about "disable" discount for point & item shop. It just simple touch, add optional flag at very last of NPC shop line. -%TAB%shop%TAB%<NPC Name>%TAB%<sprite id>,<itemid>:<price>{,<itemid>:<price>...}{,<flag>} <map name>,<x>,<y>,<facing>%TAB%shop%TAB%<NPC Name>%TAB%<sprite id>,<itemid>:<price>{,<itemid>:<price>...}{,<flag>} <map name>,<x>,<y>,<facing>%TAB%marketshop%TAB%<NPC Name>%TAB%<sprite id>,<itemid>:<price>:<quantity>{,<itemid>:<price>:<quantity>...}{,<flag>} If the flag isn't set, it doesn't bother any default NPC. Flag 0x1 = Disable Discount 0x2 = Disable Overcharge If unset, Discount and Overcharge are enabled (if available) Examples Discount & Overcharge are disabled here prontera,147,167,6 shop Shop 1 872,2102:-1,2104:-1,501:-1,3 Overcharge is disabled prontera,147,164,6 shop Shop 2 872,2102:-1,2104:-1,501:-1,2 Discount is disabled prontera,147,161,6 shop Shop 3 872,2102:-1,2104:-1,501:-1,1 When file is loaded with that flag, you will get this Info Download discount_flag-rA-20180713-ec1d6d28.diff for rAthena Git Hash: ec1d6d28 (20180713)

prontera,0,0,0 script poring_count 444,{ .@rank = query_sql("SELECT `char_id`,`char_name`,`kills` FROM `poring_kill_rank` where `kills` > '0' order by `kills` DESC", .@charid,.@name$,.@kills); .@ndx = inarray(.@name$, strcharinfo(0)); if(inarray(.@name$, strcharinfo(0)) != -1){ mes "^0024E8[YOU] :^000000 (" + (.@ndx +1) + ") : " + .@kills[.@ndx] + " Poring Kills"; } mes "[TOP 10] :"; for(.@i=0;.@i<min(.@rank,9);.@i++){ mes (.@i + 1) + " ^0024E8" + .@name$[.@i] + "^000000 ^FF0000" + .@kills[.@i] + "^000000 Poring Kills."; } end; OnNPCKillEvent: if(killedrid == 1002){ query_sql("SELECT `kills` FROM `poring_kill_rank` WHERE `char_id` = '" + getcharid(0) + "'", .@kills); if(.@kills){ query_sql("UPDATE `poring_kill_rank` SET `kills` = '" + ++.@kills +"' WHERE `char_id` = '" + getcharid(0) + "'"); }else{ query_sql("INSERT INTO `poring_kill_rank` (`char_id`,`char_name`,`kills`) VALUES ('" + getcharid(0) + "','" + strcharinfo(0) + "','" + ++.@kills + "')"); } } end; OnInit: query_sql("CREATE TABLE IF NOT EXISTS `poring_kill_rank` (`char_id` INT NOT NULL,`char_name` VARCHAR(30) NOT NULL,`kills` INT NOT NULL) ENGINE=MyISAM"); } to reset, just remove all the entries in poring_kill_rank table

you have to think about it more in my opinion before you go on with your plans and pay for anything it's a cool idea but i don't think it would work irl things to think about 1/ how many ppl would benefit from it if it's a small number it's not worth it most of the server owners have a private server to test , in local or a public/private test server 2/ script conflicting as you know most ppl would use npc_names/variables you need to think about that as a lot of people will and did do this like for example PVP_NPC/Warper/PVP Warper/PVP_System/Mvp Leader/PVP Leader etc so you need to add rules for the scripts added, and where there is rules people would try to get around it xD 3/ Pressure most scripts that are really worth adding in the server would use some calculation in x time or when x something has been done you can already imagine how many scripts would calculate something at the same time , and it's very easy to break things if you don't know what the other scripts are , not you , the scripter him self does not know what in the other scripts 4/ Testing you would need to test and approve everything in the server before it's added , or else the scripter can do some dump things to mess up the server like getting the account/pass from sql or just to mess up other scripts in the server for someone he does not like , or even to mess up the server it self like blocking all the accounts or delete all the accounts or delete all the database so it's hard to give the scripters access to the server , or else you might get to some problems , and it's easy to do something and undo it in the script so any scripter could just block everyone from the server and edit his script like nothing happen 5/ and the main point for me is the script compatibility you can't find the server that can run everything most scripters uses old rAthena version , and as rAthena is a project , there is updates all the time so some of the scripts would be out of dates or in my case , i use a lot of commands that are PR and not approved yet in rathena some users might have also src edit for the script to work 6/ Time think about how much time you would take to manage the server all the time even if you got everything working you would back to 1 and 6 (how any people benefiting from this/time) i am not trying to be negative , i just telling you to think about those things too , before you go on with your plan anyway , hope everything will workout with you.