Leaderboard

Hey guys! I'd like to showcase a script I've been busy for a while. Game mechanics is based on RWC. There are quite a lot of stuffs I modified from it tho. Here are the mechanics of the script : Maps used are 2012rwc_01-04 maps since I dont know how to make custom map xD. Anyways, here is a video on how it work in-game for better understanding. To-Do: Add registration cooldown after match [ Added ] Add points as reward [ Added ] Disable [Guild Skill] Emergency Call while on Arena [cancelled - Already available in Extended BG's MF_NOECALL ]

Hello and welcome to the continued English translation project, started by @zackdreaver. Many may know already that zackdreaver stopped with his project and that I continued with it since then. See here. First of all thanks to zackdreaver for his time and passion, which he contributed so far with his project. But since there was no one else who had a project like his or someone who took his/her time to do all this work, I thought I could take over and learned the way to do it. The result can be found at this link: https://github.com/llchrisll/ROenglishRE I made a lot of progress so far regarding translations, skill rebalances and 2020 client support. Lately I also added the required files for pre-renewal, which still follows the same format as zackdreaver's ROEnglishPRE repo, by overwriting the renewal project files with the pre-renewal files. I also have an discord server setup for faster support, issue reporting and more. Link can be found at the repo above. The difference between these two projects is also how it is installed, but to make things easier I setup a documentation site: https://llchrisll.github.io/ROTPDocs/ The actual guide can be found here: https://llchrisll.github.io/ROTPDocs/guides/install/ If you experience any trouble using this project, please use the discord server because I rarely visit the rAthena forum. Best regards, llchrisll aka Houndeye

ItemDB -> YAML! As of Git Hash: 04cfe17, rAthena's item database has been converted to YAML! What this means: The item database being in YAML format means that the database is now much more human-readable. This allows for quick review, modification, and addition of items without having to memorize the CSV format or use any third party tools. The parser now also has much better error handling when reading items into memory so tracking down those pesky typos is a thing of the past! The update combines item_avail, item_buyingstore, item_delay, item_flag, item_nouse, item_stack, and item_trade databases into the item_db so there is much less searching around multiple databases when doing anything with items! As items are no longer defined in a single row, this means the flat file has grown in size. To ease the on load text editors for people's computers who may not have the horsepower we split the items as they are in game via Consumables, Equipment, and Etc. The Job restriction for items has been cleaned up so that custom masks don't have to be made and removes a horrible restriction for those adding custom classes to their servers. Now it's as easy as defining the EAJ_* constant... and that's it! The item combo system has had a massive cleanup in the background. We no longer do sketchy memory management and manipulation with a move to use standard libraries provided by C++11! As with any YAML conversion we have provided an option in the CSV2YAML tool built right into rAthena! Just build the CSV2YAML tool within Visual Studio or via Make and run the executable. The tool will provide you with general steps and convert your custom items right on over to the YAML format. No muss, no fuss! Something that was brought up in the Pull Request was the support for SQL. Many people were against the move to YAML because the support for SQL was compromised. Well, we are happy to say that SQL is still supported and isn't going anywhere! We've developed a new tool, YAML2SQL, which can convert the YAML item database into SQL format. This allows servers who utilize SQL to continue with this method. We've also gone a step further and provided a SQL View which will create a new compatibility table without breaking support for your Control Panel/databases. The SQL View is optional though once the Control Panel/database is setup to utilize the new table. The new and fuller item data in this table also provides much more detail to the item database than ever before! You can read more details in our README! What this means to developers: Pull Requests can be reviewed much quicker and much more simpler. Identifying the actual change to the item and easily verifying said change without having to count commas! Additional features being added to the item database no longer requires the development of a side database. A vast majority of the item data is now part of the item_db structure and can continue to grow in this format! Redefined Import System: Now that the item_db is in YAML format, the adjustment of items is much simpler. If a change is being made to an item only the parts that are being changed have to be defined in the import. Below are some examples: Adjusting Red_Potion weight to 10 and increasing the heal rate in the script. - Id: 501 Weight: 100 Script: | itemheal rand(100,120),0; Remove the Thief classes from being able to equip the Cap. - Id: 2226 Jobs: Assassin: false Rogue: false Thief: false Add a stack limit of 10 to Meat for inventory only. - Id: 517 Stack: Amount: 10 Inventory: true Check out the item_db documentation for further details! Thanks to @Lemongrass, @Capuche, and @Cydh for their help!

No problem.. just a reminder that if you are using cookie-rae diff.. you will most likely encounter the bug wherein VIP accounts would not be able to login any character greater than first slot which is kind of worse than the bug of the previous source modification.. They would be able to create another character if the move character is enabled, they will simply move the first slot character and then create another character on first slot..

Make sure not select other character because i made a restriction to select other slots.

That modification has a bug wherein once you became a vip.. you are not also allowed to create characters more than 1. This modification fix that bug. // check the number of already existing chars in this account if( SQL_ERROR == Sql_Query(sql_handle, "SELECT 1 FROM `%s` WHERE `account_id` = '%d'", schema_config.char_db, sd->account_id) ) Sql_ShowDebug(sql_handle); + if( sd->group_id != 5 && sd->group_id > 0 && sd->group_id < 99 && Sql_NumRows(sql_handle) >= 1 ) + return -2; // character account limit exceeded #ifdef VIP_ENABLE if( Sql_NumRows(sql_handle) >= MAX_CHARS ) return -2; // character account limit exceeded

here bonus bDef,(50+(getrefine()/1)); bonus(bHealPower, 20 * getskilllv(SU_PURRING)); if(getskilllv("SU_SPIRITOFSEA") >= 1){ skill "AL_PNEUMA",1; }

You mean like this? prontera,156,180,3 script test 833,{ mes "[Bathory]"; mes "Eheeheeheehee! The spotlight is on Glast Heim this week, so I'm ferrying people there for a mere 1,000z!"; next; mes "[Bathory]"; mes "How about it? Want to take a ride on a beautiful Bathory's broom?"; next; switch(select("Prepare for Takeoff!:No thanks.")) { case 1: if (BaseLevel < 85 || BaseLevel > 90) { mes "[Bathory]"; mes "Come on dearie..."; mes "You must be 85~90 to enter."; close; } mes "[Bathory]"; mes "Alright, hold on tight!"; close2; warp "izlu2dun",50,133; end; case 2: mes "["+strcharinfo(0)+"]"; mes "No thanks, maybe later."; close; } } Changes if (BaseLevel < 85) { to if (BaseLevel < 85 || BaseLevel > 90) {

i guess nobody yet answer ur question. heh Networking Side well... i assume u already has successfully setup the server. just u want it to be accessible by player. in this case, u should go to router setting. then there should be menu for port forwarding just enter the ports there 6900 (login-server port), 6121 (char-server port), 5121 (map-server port) & 80 (HTTP port for website) but, u have to be sure that the ISP is allow port forwarding. if not, the connection will not be establish Server Side u should i put the Public IP on char_athena.conf and map_athena.conf (login_ip, char_ip & map_ip) how u gonna find ur public IP? simply just check link https://www.whatismyip.com/ Client SIde u should not include the Public IP in the clientinfo.xml as the public IP will changing from time to time this is called dynamic IP.. (as keep changing). NOTE: YOU CANNOT USE STATIC IP UNLESS YOU PAY TO YOUR ISP TO GET THE PUBLIC IP BECOME STATIC to check either your internet is static / dynamic IP is easy check your current public IP. then, off the modem / router for about 2-3 minutes. then, on them back & check your public IP if the public IP is same before & after u off your modem / router. then should be fine. it means that your internet is static IP but if the public IP changes after u off your modem / router, it indicates your internet is dynamic IP. to overcome the connection of the client to the server (as public IP in dynamic mode) is by using dynamic IP updater. the updater will keep checking your public IP at certain of time. and if the public IP is changed, it will update it to your domain you used. (which means u should include domain name in the clientinfo.xml) that's all.. i'll not gonna get into detail of how to setup port forwarding (Networking Side) coz in setup this, it depends on each modem / router u use. perhaps by googling / youtubing might give u clear image on how to setup port forwarding on ur modem / router. and i'm not gonna get into detail how to setup rA in ur own PC. there are lots of guidance in setup rA (both client-side & server-side) anyway, good luck!