Leaderboard

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 wiki: https://github.com/llchrisll/ROenglishRE/wiki The actual guide can be found here: https://github.com/llchrisll/ROenglishRE/wiki/Project-Guide 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!

A very good effort! However, Thor's built-in web functionality is based on an old version of Internet Explorer which throws a hissy-fit when javascript is used. @Ryoma27 If you want to stick with the built-in news feature for FluxCP, I suggest using PHP & SQL queries to extract and display the data. Or post on the FluxCP Github Issues page and request for an RSS feature ?

I don't think you can use your http://www.YOURRO.net/?module=news link, because it will always show all of your page. You need to create a separate page. I just tried it with the jQuery approach on my test server and it seems to work. Just a disclaimer ahead, I am not a web developer. Here's what I did: 1. Create a folder in your folder structure. I created it in the root directory of my FluxCP and named it patchernews 2. Create a page in your new folder. I named it news.html 3. Add these lines of code to your new page: <html> <link rel="stylesheet" href="style.css" type="text/css"> <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script> <script type="text/javascript"> jQuery(document).ready(function(){ jQuery("#newsbox").load("http://www.YOURRO.net/ #newscontent"); }); </script> <div id="newsbox" style="width: 600px"></div> </html> What we do here is place a div with the ID "newsbox" on our new page. Set width: 600px to the width of your notice box in the Thor patcher. We then load the content of your news from the URL "http://www.YOURRO.net #newscontent". Set the URL to wherever your news are displayed on your site, but keep #newscontent. Of course, this only works if you have a div on this page with the ID newscontent. 4. So we will wrap a div with the ID newscontent around your news table. Go to the page where your news are displayed and place <div id="newscontent"> at the beginning and </div> at the end. 5. Go back to news.html and link to the stylesheet you wanna use. Replace href="style.css" with e.g. "../themes/default/css/flux.css" if you are using the default theme of FluxCP. You can also create a new style.css file in this folder and style the page yourself. This way you have more control over how exactly it should look in that small notice box within the patcher. 6. Change the URL for the notice box in Thor's config.ini to 'http://www.YOURRO.net/patchernews/news.html' Let me know if it works.