Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/19/16 in all areas

  1. We here at rAthena believe that the users have the right to know what our team believes this project should be. rAthena Goals: Emulation AccuracyOur top priority of this project should be put towards creating an experience that matches that of the official servers. Right now, we are far from reaching that goal, but with focus on this particular issue, and with the help of people like you, we can close the gap between the official servers and ourselves. While this may never reach 100% accuracy due to constantly changing aspects in official servers, we could definitely do better than where we are right now. StabilityWhile we continue to fix bugs and add additional new content, it is extremely important that we remain focused on creating a project you can rely on to manage itself while you are away from your server. We want you to feel comfortable walking away knowing that you won't come back to a downed server. Resource ConsumptionCode speed and resource reduction should remain a lower priority as accuracy and stability are more important than saving some memory or process time. A successful project requires this understanding. Sometimes we may improve code that we come across during fixing other bugs or re-writing sections of code, but at this time, we should not focus on finding and fixing some of the more resource consuming portions of code. CustomizationWe're "core" developers. We develop a platform for people to build off of. Out of the box, we aim to maintain parity with AEGIS, and beyond that, we will provide tools and support (as long as it doesn't detract from the core!) for people aiming to customize beyond that. Anything our users make and wish to have added to the public source also needs to be approved and improved on an individual basis. If you're looking to start up a server project which follows the above principles, then rAthena is the project for you.
    1 point
  2. Use the tool 'Search'. You'll find the best
    1 point
  3. First, You have to know which warp point you want to disable. Then use disablenpc instance_npcname("warp name") then add a trigger script to enable it. base it here: https://rathena.org/board/topic/92382-disable-warp-on-instance-dungeon/#entry243658 as an example: prontera,150,150,0 script Instanced Prontera#a 101,{ set .@instance$, "Primer Jefe"; if (instance_id()) { if (select("Enter Instance.:Cancel.") == 2) end; if (instance_enter(.@instance$) != 0) { mes "Instance entrance ^FF0000failed^000000."; close; } } else { if (select("Create Instance.:Cancel.") == 2) end; if (instance_create(.@instance$) < 0) { mes "Instance creation ^FF0000failed^000000."; close; } mes "Instance created."; close2; instance_enter(.@instance$); //this .@map$ = instance_mapname("prontera"); .@label$ = instance_npcname(strnpcinfo(0))+"::OnMyMobDead"; monster .@map$,0,0,"--ja--",1002,150,.@label$,2; //end } end; //this OnMyMobDead: enablenpc instance_npcname("warppoint name"); end; //end OnInstanceInit: disablenpc instance_npcname(strnpcinfo(0)); //this disablenpc instance_npcname("warppoint name"); //end end; }
    1 point
×
×
  • Create New...