Leaderboard

Hey guys! I've been receiving many PMs over the last two months from disgruntled members claiming that staff are being unfair or giving out Warning Points on a whim, so I thought it might be time to explain how this system works. The Warnings available to staff are all preset in order to have a standardised rule set. All staff are unable to make up their own warnings to prevent bias. These warning reasons are taken directly from the Rules page, which all members agree to adhere to. Each warning has a +# value in front of it denoting how many warning points it gives. When your account has reached a certain number of points in any 28 day period, your account will suffer under some restrictions. These restrictions are also preset. For example, for breaking the rules for topic bumping 5 times within any 28 day period will restrict you from posting on our forums for 7 days. The rules predate my existence on this project and i'm sure many members who have been a part of this project can agree that over the last few years we have become ignorant of punishing rule-breakers. I believed our laid-back lax approach needed a gentle push, so this system was overhauled on 7th December 2016 and is so far doing it's job very well. December Warnings: 40 January Warnings: 69 The staff are not out to get you and only issue warnings if the warning conditions are met. Members who don't follow the forum rules get warned, it's as simple as that. If for some reason you believe you shouldn't have been given warning points in a particular instance, please feel free to contact me.

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.

It is a custom backup solution I've been working on, Thanks to feedback of community, I managed to make a V2 V2 of my Database Backup solution Featuring 1. generate a backup of databases specified in a list 2. Name them with yyy-mm-dd[DatabaseName] format 3. Compress them into .7z using maximum compression 4. Set a password on .7z archive 5. Send them to cloud storage Google Drive 6. Write logs 7. Removes all compressed backups 28 days or older (keeping local folder nice and clean) 8. Can be automated with cron to run even every 12 hours Ow yeah, Don't worry about someone hacking your GoogleDrive, if you put 14 character+ Alphanumeric password on yout backup archives it is going to be bruted loong time...

April Digest 2017 The following digest covers the month of April, 2017. Staff Changes Jeybla is now a Core Developer srhmike is now a Forum Moderator Sryx is now a Forum Moderator Cyro is now a Forum Moderator Technoken is now a Forum Moderator Promise is now a Forum Moderator Development Highlights CORE: Fixed Storage bug (c218eb6) Added cash shop support to 2012-04-10 (3cce333) Fixed a bug with Renewal table loading (ec1fe15) Added new script command: chatmes, getfreecell (72fe4cd, 0c2ccc7) Re-link monster drop data with item data (d6594ee) Fixed sleep times getting freed twice (4b9ade3) Fixed debug output for missing char server tables (780ebd1) Removed password outputs on login server console (100d71e) Added current_equip_item_index check (384917b) Adjusted Status Change display in status window (a75133e) Removed empty script check for usable items (38e0496) Implemented Channel System expansion (c87dba5, c3ad04d, 4f99567) Fixed Blessing ending Curse before the Curse check (f1af321) Updated Homunculus-S skill failure messages (452d9c6, b4857cc) Added deprecation functionality to script engine (5923633) Removed unnecessary library includes (4cfaa18, 31cd394) Initial release item Random Option for monster drop (e59cdff) DATABASE: Skill update: Claymore Trap, Blast Mine, Land Mine, Monster's Bombs, Feint Bomb, Stealth Field, Neutral Barrier, Pain Killer (5d90380, 0a35e3a, 1261d92, caed389, 800f491, cbc3b26) Item DB updated (f0b7feb, a040a52) Expanded Baby Jobs (39e54d6, b7d802a, 2029f2e, ad0731f, ed24be1) Added missing Quest ID in quest_db.txt (f57f3e7) Added support for the latest NPC and Mob IDs (7d20033, 25da0fe) Adjusted skill_nocast_db settings (a7c682f) SCRIPT: Fixed a bug in Sara Memory (a6b252c) Removed extra semi-colon from multiple scripts (73b798b) Updated DTS Warper in moc_ruins map (3986195) Fixed wrong condition in monk.txt (c098d0c) Converted some scripts to warps (cdc0527) Fixed a bug in Continental Guard NPC (9e6b02a) OTHERS: Updated Instancing document (82967fc) Fixed a compile warning and error (4369b47, f9a0f81) Removed ancient SQL Upgrade files (9af37d2) Updated default PACKETVER to 55 -> 20151104 (33c31ca) Fixed misc grammar on documentation (58bad46) Removed rAthena-15.sln (da36b26) Updated appveyor.yml to use new solution (7fb245b) Added missing EOL in project files (fcba7b7) Moved the .bat scripts into the tools folder (448e5e8) Updated gitignore for the moved shell scripts (3995fff) Redirected build output into the .vs folder (bfeb697) Added a -D equivalent for msbuild in Appveyor (4348ef3) Added Visual Studio x64 support (07b2ef2) Removed dbghelp.dll (be9b13d) Enabled x64 in Appveyor (4a64986) Statistics Excluding merges, 12 authors have pushed 67 commits to master and 132 commits to all branches. On master, 295 files have changed. There have been 25,469 additions and 18,650 deletions. There are 23 merged Pull Requests and 15 Proposed Pull Requests. There are 24 new Issues and 41 Closed Issues. List of Contributors @Akkarinage, @aleos89, @anacondaqq, @Atemo, @CairoLee, @crazystorm2017, @cydh, @Encon21, @Everade, @feltenc, @hazimjauhari90, @Jeybla, @Joy-Ro, @Lemongrass3110, @LiamKarlMitchell, @Limestone, @MishimaHaruna, @MrAntares, @Playtester, @spangler88, @technoken, @TheNoobCompany, @Tokeiburu, @secretdataz, @stealth62, @wilkemeyer, @Yuchinin Show your support to rAthena by submitting your Issue or Pull Requests! By providing enough useful info (Git Hash, Client Date, RE/Pre-RE, crashdump, how to reproduce, etc) you will help us to solve the issues faster

Dear guys who have their own gcc/clang solutions to compile rathena code on windows platform, please share it with community and make a topic here about it, don't be badass. I will for sure solve it and make a release but after a long time because of my overhead & business now. Maybe you can help and do it earlier them me? The short info why I'm asking it stored here: https://github.com/rathena/rathena/pull/2089 tl;tr goal what possible to achieve with portable gcc\clang is 50-150mb folder with all components required for rathena compilation. It saves time, internet BW, space on SSD for people who need just make from sources - executable application need 99% of functions from Visual Studio. Or maybe is here another solution exist to solve the problem above? EDIT: done, but not gcc, but very usable

Lesson learned.