Leaderboard

Officially supported client versions and changes to support policies on client-related bugs Hello! Here at rAthena we try our best to provide a stable server to build around. Unfortunately we've had a rash of commits in the past few months that have introduced client bugs that hadn't existed before. This is unacceptable and we apologize for any downtime or issues this may have caused. There has also been a large number of bug reports involving unusual client versions, resulting in significantly wasted time and effort on our behalf trying to track down bugs that may or may not actually exist. So as such we have as a team decided to tighten down the list of officially supported clients for rAthena. These clients will be tested against on any major update or commit that affects any packet or client-facing code to make sure new bugs are not introduced. Other client versions will be supported on an as-is basis. Basically, you are free to use any client version you wish, but for stability reasons we highly recommend sticking to the officially sanctioned list as those will be the ones we test against. If an update breaks support for a client that isn't on the approved list then it may be taken care of at a lower priority than bugs affecting officially approved versions. This does not mean we will intentionally be breaking support for clients that are not officially sanctioned, this merely means support will be tailored to those first and foremost, and any bugs or bad behaviors may go unnoticed or corrected. If there any conflicting changes that would break support on one of the officially sanctioned versions, those bugs will definitely not be fixed. What does this mean to you, the server admin? It means you can pick from one of our officially supported client versions and rest assured we will tailor support specifically to those and will aim for stability for those clients. We will do everything we can to make sure client bugs are not introduced during updates so you don't have to waste your time troubleshooting, or have to deal with angry players if something breaks. And in the unlikely event something does break, we will put the highest priority on fixing bugs affecting the officially supported clients. Here are the following clients and which server mode we support them for. Pre-Renewal: 2010-07-30aRagexeRE Renewal 2012: 2012-04-10aRagexeRE Renewal 2013: 2013-08-07aRagexe 2013-12-23aRagexe Renewal 2014: 2014-10-22aRagexe Renewal 2015: 2015-05-03aRagexe 2015-11-04aRagexe We are not supporting 2012 era Ragexe clients, only RagexeRE. Use those at your own peril. Bug reports for any other client will only be accepted at a core developer's discretion, if at all. We reserve the right to close and ignore any bug reports coming from clients other than the ones listed above. Clients older than 2010-07-30aRagexeRE are considered depreciated and while they work for the time being, support may be removed at any time. It is highly recommended you move your servers to 2010-07-30aRagexeRE or newer as soon as possible. An announcement will be made if support for clients older than 2010-07-30aRagexeRE is intentionally removed, but be warned it may break at any time and bug reports will not be accepted for fixing them.

Hello nice people! Besides mapping, I also enjoy to do some web layouts, just for fun. Days ago I was talking with @KamiShi and this web layout I'm showing here is going to be coded and flux integrated by drawmove soon. Once it is coded it will be great, with dynamic content everywhere. I did this one by the idea to make it clean, discreet & professional; with the fact about keeping functionality/content as a priority rather than a fancy look. This is the second time in my life I do flux theme and the first one I show. Please rate if possible! I need your rating and comments to improve it, and do better ones the next time! Thank you. Full size ---> https://dl.dropboxusercontent.com/u/52175822/web2_showcase.jpg

Hello, Since I'm almost done making my GRF Encryptor/Decryptor + Client Configuration , I made a new Project which can prevents hack tools to help rathena members whom cannot afford buying such as Harmony. And im willing too to implement Auto-Ban when using hack tools. So , now i have started adding some source code but , i am still analyzing and studying each of the code written in every source code file. Now , What im gonna asking to all if you can also share what you have learn in every source code file especially to the Community Contributors about the functions to reduce my time studying/analyzing the code. . I would appreciate and glad to those who will share their learning's about this. Just PM me and Feel free to share your knowledge about the source code functions . Thanks

Hello everyone Before introduction, I apologize for my poor english... If you find something mean weird, please let me know. ------------------------------------------------------------------------------------------------------------------ Started: - 20/06/2013 Developer: freeman129 General Info: Items's price would change, when someone buy/sell them. Player buy many A items, and then the A item's price will be increase. Player sell many B items, and then the B item's price will be decrease. Main System: This inflation is linear formula, new_price = new_price + origin_price * buy_sell_change / inflation inflation var. is constant and it according to item's type. Init: -0.5*inflation <= buy_sell <= inflation show diagram below: ------------------------------------------------------------------------------------------------------------------ If someone buy/sell, server will add/minus sum of arithmetic sequence to your deduct/get money. The sum of arithmetic sequence just like the area of ​​the triangle. ex: If someone buy many A items and then sell all A items, just like diagram below: ------------------------------------------------------------------------------------------------------------------------------------- Other Mechanism: This system add auto-recover function, it means, manager can set timer to recover the changed items(be close to origin price). File Modification: I modify some file in conf/ conf/battle/ src/map/ src/config/ I also modify itemdb datastructure, I add 3 data are 'origin_value_buy' (int). 'inflation' (int) and 'buy_sell' (int), and change 2 data structure are 'price_buy' (float) and 'price_sell' (float). This version , dbs must on sql. Test Video: Download: Github (Git clone from rathena github, and then git push origin master on my github with inflation.) This project is not perfect, so welcome to modify it to perfect. If you want to use that, please back up your original version! and you must use item_db_inflation_re . mob_db_re and mobskill_db_re on sql. Thank you for reading~

works like a charm

it's removed....because...it make no sense if an equip that you currently wearing is non-identified. so you can just simply remove that part from your script ...

there is no "getequipisidentify" if rAthena. but it exist in hercules. Maybe this script is from hercules? you can remove this line and it will load perfectly but it will remove the check if item is identified function

yep here is error what he drops when im using a Shop, hes not clearing the SQL DB after closing a shop [SQL]: DB error - Duplicate entry '150000-0' for key 'PRIMARY' [Debug]: at vending.c:311 - INSERT INTO `vending` (`char_id`,`name`,`index`,`nameid`,`amount`,`price`,`refine`,`card0`,`card1`,`card2`,`card3`) VALUES (150000, 'sdsadasda', '0', '1101', '1', '100000', EDIT the problem only happens when using AUTOTRADE , then de dont remove the SQL entrys when u log back in How to Reproduce: 1= Open a shop and use @autotrade 2= log the char back ingamge 3= Open a shop and use @autotrade 4= you will have now a Error in map serveer

My server's goal matches this 100%. No customizations, no deviations from official behavior. If you (the rAthena devs) need a guinea pig server, we (my server/community) are willing to help anywhere possible.

you need a new script command to check http://www.eathena.ws/board/index.php?showtopic=271354