sader1992

*setcell "<map name>",<x1>,<y1>,<x2>,<y2>,<type>,<flag>; export_constant(CELL_SHOOTABLE); try this (didn't test this) setcell "prontera",0,0,100,100,CELL_SHOOTABLE,1;

yes file not found @Akkarin

plz open new post with all the info of your problem to get help faster

the url working for me

GitHub\rathena\db\castle_db.txt

yes

you already did a video you should make it for more then 1 npc in the normal stat i will ask you to but the script for this npc to let us check it (the npc in the video) i would also ask you what version you use from rathena (hash) what happen in the terminal when you talk to the npc ? renewal / pre-renewal ? client side exe version ? what npcs you have this problem in ? if there is many (else then the one in the video) link the npcs you have the problem in ? and check this

this makes me happy :3

if you have old rathena i would suggest you upgrade your rathena cuz you would need alot of edits and if you have the lastest rathena there is no need to edit the files anymore they already add support for the client so you can use it just by editing your #define PACKETVER 20170517

query_sql( "SELECT `clothes_color` FROM `char` WHERE `char_id` = '"+.@charid+"'",clothesc ); this line save the value of the color in a char variable (clothesc) this mean that if the color value 5 clothesc will also be 5 and now you can call clothesc without sql cuz it's a variable by just typing it so if after you call the func SaveClothes and the cloth color was 23 if you but npc say mes clothesc; the npc will say 23 and in the unequip you are setting the color to clothesc value so it will be 23 if you call the sql line in equip again in unequip that what will happen you are setting clothesc to the color value (let's say 23) when equip then the style change and the color for the new style will be 0 and when unequip the sql will be called again and will save clothesc color as 0 from the new style and remove the old value from it and you will end up with the color 0 after unequip

^^^ the new prontera is the old prontera now

I have to say this gives me an idea XD but yah good idea if rAthena did it officially cuz even if i done with it ,there is things that i can't do like reading the map_cache.dat

function script SaveClothes { // Save Clothes Color .@charid = getcharid(0); query_sql( "SELECT `clothes_color` FROM `char` WHERE `char_id` = '"+.@charid+"'",clothesc ); setlook 7,0; setlook LOOK_BODY2,1; } function script PutClothes { // Put Clothes setlook LOOK_BODY2,0; setlook LOOK_CLOTHES_COLOR,clothesc; }

// Save Clothes Color == the player equip the item ? // Put Clothes == unequip ?

i think you need 201705 and more for that

the sql update when you login or when you use the script you just need to make sure that the line called everytime you want to save new value so i see here in the photo you are using another style and when you back to your style you back to the old color try that>> when you talk to the npc he will save the color value first then he will ask you to change your style ? ok change your style and when you get back to your old style make the npc restore your color after he gives you your old style back if you put the script it would be easier for us

.@charid = getcharid(0); query_sql( "SELECT `clothes_color` FROM `char` WHERE `char_id` = '"+.@charid+"'",.@clothesc ); now .@clothesc = the color you can save it to char variables or else where and call it when you want it if you put the script here it would be easier for us to help

I don't know what Bro but rAthena follow Kro and this is a client side error not server error so everything work fine in rAthena

make sure they are in the instance_db.txt (all their maps) and that their quests in the quest_db.txt if you are using pre-renewal you have to add them in instance_db.txt cuz they are not by default

- script pvp_map -1,{ OnPCLoadMapEvent: getmapxy .@ma$,.@ax,.@ay,0; if(.@ma$ == "pay_fild08") { message strcharinfo(0),"The map is currently in PVP mode so be ready!"; } } pay_fild08 mapflag loadevent

switch (BaseClass) {case Job_Acolyte: bonus bAllStats,10; break; case Job_Thief: bonus bAllStats,20; break;} if Acolyte and up 10 all stats if Thief and up 20 all stats

only champ and only thief ? or up and down classes ?

you can use switch (BaseJob) or switch (BaseClass) if you want