Leaderboard

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!

View File Simple Client-Side Generator [itemInfo/accName/accessoryID] Hello rAthena! I have been struggling with adding large amounts of custom items into my client-side, so I made a little tool that would help with just that, and I'd like to share the tool with the community! I will continue to update this project over time; adding a user interface & specific parameter options. Important Reminders: - You need the latest Java Verison to run this program. Download: JDK 15 Download - Both input_sprite.txt & input_display.txt must have the same number of lines. - input_sprite.txt MUST have a underscore (_) for white spaces. - If there is one-character-value or less in the input_sprite.txt & input_display.txt files, that line will be omitted with a empty line. - Once Java has been installed, you must use the run.bat file to open the program. Helpful Articles: - How to Open Jar | Reference: https://www.wikihow.com/Run-a-.Jar-Java-File - Java SE Downloads | Link: https://www.oracle.com/java/technologies/javase-downloads.html Click for Demo Video Submitter Katazui Submitted 11/18/2020 Category Client Tools Video https://www.youtube.com/watch?v=_8egrn397-M Content Author Katazui  

View File Free skin Thor Patcher 2020 Holidays [CODED] Please - Do not remove credits - I do not authorize the sale of this launcher Content - Thor Patcher [CODED] - PSD Project - PHP Files Server Status + RSS Feed - This file has a configuration guide Guide.txt Buy me a Coffe *u* Support Discord: єℓƒιη#9444 Powered by @Aeomin & Design @Elfin Enjoy and happy holidays ? Submitter Elfin Submitted 11/12/2020 Category Patchers Video Content Author Elfin & Aeomin  

Thanks for pointing this out functor.

You need to create entries for your garments in spriterobeid.lub (where you assign it's view ID similar to accessoryid.lub) and spriterobename.lub (where you assign the ID to a resource like accname.lub) it's pretty self explanatory when you open the lubs. Both lubs can be found in your datainfo folder. This would be your entry for the wings you are trying to use (directly from kRO). spriterobeid.lub ROBE_WINGS_OF_FALLEN_ANGEL = 3, 3 would be your view ID for your DB entry (you can change the ID if you wish). spriterobename.lub [SPRITE_ROBE_IDs.ROBE_WINGS_OF_FALLEN_ANGEL] = "타락천사의날개", Make sure to put the name entry in both tables RobeNameTable and RobeNameTable_Eng.

@JackTheGorrion You need to update Java. It is from your video: