Yommy

Yommy was just awesome this month (as usual)
<3

Yommy was just awesome this month (as usual)
<3

Yommy was just awesome this month (as usual)
<3

Yommy was just awesome this month (as usual)
<3

Yommy was just awesome this month (as usual)
<3

this requires a large client modification. here is a new version.
and i doubt it will be made public
 
http://www.ragnarok-online.org/charcreate.html

this requires a large client modification. here is a new version.
and i doubt it will be made public
 
http://www.ragnarok-online.org/charcreate.html

Classy,
Something that annoys me is sprite errors. So it could also sanity check every item
To make sure they have the required sprites and images

name=사라 - 만18세이상
usercount=239

name=다크로드
usercount=25

name=바포메트
usercount=1417

name=란드그리스
usercount=156

name=타나토스
usercount=222

for anyone who requires, the 3 keys are hardcoded to each client, you can search the keys in hex editor and modify for something unique.
for those with IDA / OllyDBG, the keys are pushed just before the PACKET_CZ_ENTER reference (not the actual string)
 
.text:007962A7 0F 84 77 FC FF FF jz loc_795F24 .text:007962AD 8B 0D 04 0F 98 00 mov ecx, dword_980F04 .text:007962B3 68 05 22 05 22 push 22052205h // key 3 .text:007962B8 68 05 22 05 22 push 22052205h // key 2 .text:007962BD 68 05 22 05 76 push 76052205h // key 1 .text:007962C2 E8 A9 64 E3 FF call sub_5CC770 .text:007962C7 68 6C 30 89 00 push offset aPacket_cz_ente ; "PACKET_CZ_ENTER" .text:007962CC E8 6F 19 C7 FF call nullsub_1 .text:007962D1 B9 2D 02 00 00 mov ecx, 22Dh .text:007962D6 83 C4 04 add esp, 4 .text:007962D9 66 89 4C 24 48 mov word ptr [esp+3ECh+cp+2], cx

either request at rAthena to convert it, or change to using Hercules
 
Hercules devs will not create this for rAthena o_O

either request at rAthena to convert it, or change to using Hercules
 
Hercules devs will not create this for rAthena o_O

either request at rAthena to convert it, or change to using Hercules
 
Hercules devs will not create this for rAthena o_O

either request at rAthena to convert it, or change to using Hercules
 
Hercules devs will not create this for rAthena o_O

either request at rAthena to convert it, or change to using Hercules
 
Hercules devs will not create this for rAthena o_O

for anyone who requires, the 3 keys are hardcoded to each client, you can search the keys in hex editor and modify for something unique.
for those with IDA / OllyDBG, the keys are pushed just before the PACKET_CZ_ENTER reference (not the actual string)
 
.text:007962A7 0F 84 77 FC FF FF jz loc_795F24 .text:007962AD 8B 0D 04 0F 98 00 mov ecx, dword_980F04 .text:007962B3 68 05 22 05 22 push 22052205h // key 3 .text:007962B8 68 05 22 05 22 push 22052205h // key 2 .text:007962BD 68 05 22 05 76 push 76052205h // key 1 .text:007962C2 E8 A9 64 E3 FF call sub_5CC770 .text:007962C7 68 6C 30 89 00 push offset aPacket_cz_ente ; "PACKET_CZ_ENTER" .text:007962CC E8 6F 19 C7 FF call nullsub_1 .text:007962D1 B9 2D 02 00 00 mov ecx, 22Dh .text:007962D6 83 C4 04 add esp, 4 .text:007962D9 66 89 4C 24 48 mov word ptr [esp+3ECh+cp+2], cx

for anyone who requires, the 3 keys are hardcoded to each client, you can search the keys in hex editor and modify for something unique.
for those with IDA / OllyDBG, the keys are pushed just before the PACKET_CZ_ENTER reference (not the actual string)
 
.text:007962A7 0F 84 77 FC FF FF jz loc_795F24 .text:007962AD 8B 0D 04 0F 98 00 mov ecx, dword_980F04 .text:007962B3 68 05 22 05 22 push 22052205h // key 3 .text:007962B8 68 05 22 05 22 push 22052205h // key 2 .text:007962BD 68 05 22 05 76 push 76052205h // key 1 .text:007962C2 E8 A9 64 E3 FF call sub_5CC770 .text:007962C7 68 6C 30 89 00 push offset aPacket_cz_ente ; "PACKET_CZ_ENTER" .text:007962CC E8 6F 19 C7 FF call nullsub_1 .text:007962D1 B9 2D 02 00 00 mov ecx, 22Dh .text:007962D6 83 C4 04 add esp, 4 .text:007962D9 66 89 4C 24 48 mov word ptr [esp+3ECh+cp+2], cx

for anyone who requires, the 3 keys are hardcoded to each client, you can search the keys in hex editor and modify for something unique.
for those with IDA / OllyDBG, the keys are pushed just before the PACKET_CZ_ENTER reference (not the actual string)
 
.text:007962A7 0F 84 77 FC FF FF jz loc_795F24 .text:007962AD 8B 0D 04 0F 98 00 mov ecx, dword_980F04 .text:007962B3 68 05 22 05 22 push 22052205h // key 3 .text:007962B8 68 05 22 05 22 push 22052205h // key 2 .text:007962BD 68 05 22 05 76 push 76052205h // key 1 .text:007962C2 E8 A9 64 E3 FF call sub_5CC770 .text:007962C7 68 6C 30 89 00 push offset aPacket_cz_ente ; "PACKET_CZ_ENTER" .text:007962CC E8 6F 19 C7 FF call nullsub_1 .text:007962D1 B9 2D 02 00 00 mov ecx, 22Dh .text:007962D6 83 C4 04 add esp, 4 .text:007962D9 66 89 4C 24 48 mov word ptr [esp+3ECh+cp+2], cx

what a fine idea.
any other topics or questions regarding rAthena downtime will result in bad things
 
they already stated they are restoring from some backup, and are posting updates at http://bit.ly/10FLL14
after this whole episode, their admin abilities should be regarded as questionable.

what a fine idea.
any other topics or questions regarding rAthena downtime will result in bad things
 
they already stated they are restoring from some backup, and are posting updates at http://bit.ly/10FLL14
after this whole episode, their admin abilities should be regarded as questionable.

Frequently Asked Questions (FAQs):



I thought splitting this section from the main post would be beneficial because it's easier to write it and to look in it in case you need an answer and I have it down there.



I hope there are almost no questions because I think my guide is clear enough, though it's normal there will be some questions out here since my explanations aren't perfect. That's why this dedicated section exists.



Questions will be marked with a big Q and answers will be marked with a A. Both will be big enough to easily tell them apart.



Question list:
Questions & Answers:



Q: I get a warning message while trying to make a Pull Request on GitHub. What happens?

A: You can't make a pull request if you get a warning message from GitHub. Those messages usually provide enough information to tell you what to do. Here are all warnings I've received from GitHub to date and its possible solutions – just remember to change HerculesUser to your GitHub username–:
Oops! HerculesWS:master is already up-to-date with HerculesUser:master Try a different branch?You haven't pushed any changes to your remote repository or the changes you've pushed make it identical to the original Hercules repository. You can only make a pull request if your repository is not exactly the same as the original Hercules'. Oops! There's already a pull request for HerculesUser:master Try a different branch or view the pull request?You already have an active pull request on Hercules and you have to wait until it's approved or rejected. If you want to add changes to your pull request, you can push more changes to your repository if you want: they'll automatically be added to your active pull request. Q: How do I update my fork to Hercules' last version?

A: This is quite simple but not as easy as updating an official Hercules repository as you can't just pull as you did when updating the original Hercules repository – if you try to pull on your fork you're pulling from your fork's repository, not Hercules' –. Doing this task also depends on your OS:
On Windows: (I don't deem necessary to add a how-to picture for this)Right-click your Hercules fork folder and select Fetch... option from the TortoiseGit submenu. A new window will pop up. Select Arbitrary URL option and place original Hercules repository URL there (I mean this one: https://github.com/HerculesWS/Hercules.git). Then click OK (unless you want to change any of the available options, which is unfrequent) for making the fetch update to start. Another window will be opened and your fork will be updated to Hercules last revision. Close it once you're done. On Unix: You just have to run this command (it's actually two commands joint on a single shell statement): git fetch upstream && git merge upstream/master Just remember that if you want these changes to also be on your GitHub repository, you'll have to push them. Otherwise they'll just be available on your local repository, as always.



Q: I always get an error message whenever I try to push my changes even though I make sure I put correct access credentials. What happens?

A: I've just experienced this error when I tried to push to the wrong repository (i.e. the original Hercules repository, to which I don't have access and you surely don't). Make sure you're trying to push to a repository on which you have permission for this. Ah! Also make sure you have an active Internet connection since you'll be using it!



Q: I can't commit anything to my local repository. What happens?

A: Chances are you're trying to make a commit without changing any file, and that's not possible for Git. Maybe you actually changed some files but forgot to save them?

Do you remember the many advantages Git has against Subversion (SVN)? One of those many advantages is the fact that in Git, you can send pull requests in order to directly collaborate with the community, without even the need of being an official Hercules dev, and if you contribute enough you can surely become a dev if you want. Well then, this is an – as detailed as possible – guide on how to make them.
 
First of all: What is a pull request? It's a way of telling the original devs of a (commonly open-sourced) project what changes you've made yourself on their project supposedly for the better, and kindly ask them (request) to merge it (pull). In short, it's a way of collaborating to a project without the need of being related at all to it. Obviously, your pull request may be rejected if it doesn't meet some requirements, but this is another story.
 
Git does also offer its own tools for pull requests (more info), but they're incompatible with the ones GitHub has. Moreover, GitHub pull request tools are easier to use than Git's.
 
What steps are required in order to do a pull request? In abstract, you'll have to:
Sign up for a GitHub account, if you don't have it already. Fork Hercules project in GitHub, if you haven't done this already. Clone your previous fork to a local repository in your computer, if you haven't done this already. Work on your fork. Commit your changes to your local repository. Push the changes you've previously committed to your remote repository on GitHub. Make the aforementioned pull request to the Hercules official repository. Steps 3 and 5 have already been shown on the Obtaining Hercules guide by @Ind (Obtaining Hercules through Git on *insert OS here* and Troubleshooting sections). These two steps will be slightly reviewed, but expect a fully detailed how-to in the others.
 
By the way, GitHub also has its own (generic) guides on how to fork a repo and then make a pull request, which also explain the toughest parts of this guide (though they're not so tough) and cover steps 2-6 (supposing you have a Git console). You're encouraged to go and read them if you want.
 
Well, here we go with the guide!
 
Step 1: Sign up for a GitHub account



Step 2: Fork Hercules project in GitHub



Steps 3 to 6: Local computer work



Step 7: (Finally) submitting the pull request


 
Congratulations! You have successfully made your first pull request on Hercules! This is a reason to be proud of yourself, isnt it?