Leaderboard

This is such a minor tweak that I don't even really think it's worth creating a topic for, but my testers reported that this makes the game feel significantly smoother. This change attempts to address a desync issue when attacking. When clicking on a monster that is hostile and is also moving towards you, sometimes your character will fail to begin attacking because the client thinks it is within range to attack, but the character is actually too far away to attack on the server side. It's especially common with monsters that move fast. With this tweak, this situation should no longer happen. The change is in unit.cpp: Find this comment: // Player tries to attack but target is too far, notify client Add this line immediately afterwards: clif_fixpos(src); // synchronize the player's position with the client Don't change anything else. The finished code block should look like this. if(sd && !check_distance_client_bl(src,target,range)) { // Player tries to attack but target is too far, notify client clif_fixpos(src); // synchronize the player's position with the client clif_movetoattack(sd,target); return 1; Then just recompile the code and test it out. Everyone I had test it said it felt instantly noticeable. This does increase the number of packets being sent so this may cause a very minor increase to network traffic, but based on the number of packets that are typically sent back and forth I don't think the effect is very significant.

Afternoon everyone! Many moons ago we migrated our wiki content to Github in an effort to alleviate resources on our VM, increase our data's stability and in-general, significantly reduce the number of things that could go wrong. That was the plan. The plan worked well enough on all three counts above, however, Github Wiki's have this wonderful knack of not doing what they're supposed to when you need them to be helpful. For example, users needing special permissions to push new content to it (until very recently this has been "maintainer" access only), which means everyone has to rely on rA Staff to update the Wiki, which we evidently haven't had much time for. Now there's a new kid on the block; User-Guides! Guides from the Wiki will slowly be migrated to our new User Guides site (which you can help with, if you want to), which is a HTML website hosted using Github Pages, automatically generated from Markdown files that are stored in a Github Repository. Neat, huh! View the site at https://rathena.github.io/user-guides/ Because this new guide platform is built on a git repo, it means that anyone can contribute to it by opening a Pull Request. I've written some guidance here: https://github.com/rathena/user-guides/blob/master/CONTRIBUTING.md "What about all those guides on the forums" I hear you ask. Let's face it, 20% of them don't make any sense, 30% of them are inaccurate, 90% of them are outdated, 100% of them are developed with either bias towards specific software tools or just badly written due to language barriers or laziness. Far too often are links to out-of-date guides re-posted on the forums and in Discord, and we can't keep them updated because they're forum posts so only Mods can edit them (which is not what they're here for). From now on, well-written guides are to be posted to the User Guides repo. Guides posted on these forums will result in a message being sent to the author stating why we're going to hide the thread and then give a link to this post. What can you NOT post to User Guides? rAthena is a software emulation project. As such, guides pertaining to 3rd Party Tools or software will not be approved. This includes "How-To's" regarding the client, which is not actually within the scope of the rAthena project. We don't want to be sued ?, thanks. We have a new channel in Discord called #user-guides for discussions related to this area of the project. We would be very happy to see you helping our effort to migrate and write good, informative guides for our community to use and keep updated for years to come! Next we'll be working on doing something very similar to our source's /doc/ directory! Akky~