Akkarin

Yes. Read the instructions for the software tool you're using.

rAthena takes "too long" to merge pull requests because too few people bother merging, testing, giving us their results. There are plenty of guides around on how to merge Pull Requests: https://help.github.com/articles/checking-out-pull-requests-locally/ https://gist.github.com/piscisaureus/3342247

There's no single solution to this as there are many aspects to running a VNC server that affect how this would be setup. For a basic example though, you can look at these: Desktop shortcut file (start.desktop) [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=Start rAthena Type=Application Terminal=false Exec=/path/to/scripts/start_server.sh Icon=/path/to/icon.png start_server.sh #!/bin/sh DIR=/path/to/scripts xterm -title "Login Server" -bg black -fg white -hold -e $DIR/start_login_server.sh & start_login_server.sh #!/bin/sh cd /path/to/rAthena ./login-server There are a great many guides on the internet that can walk you through setting up a VNC server and then configuring it to run scripts based on desktop shortcuts.

As i said, the error is telling you which file is the problem. It's even telling you which line the issue is on.

There are 20+ guides on client setup - the more relevant guides are in https://rathena.org/board/forum/99-client-releases/

Not really sure why you're copy pasting config files when the error is given to you in the consoles, and if you read it you'd be able to fix it. Also, use code box in future.

Not really sure why you're only pointing 1 server out in bold.. I know of atleast 6 that have rodex fully implemented. NovaRO is actually the only server that does their own research on kRO and then gives their findings to the rA dev team, since it's owner is one of our devs. Looks like your post needs rewording.

RODEX is still being completed, while the old mail system isn't compatible with newer clients because of RODEX being introduced. Everyone seems to be waiting on the Devs to add new features. This would be sped up by people testing on official servers and providing packets, screenshots, replays, video files - anything to help the devs. Most server owners seem to be able to add their own content based off official servers before rAthena gets it because they do their own background work and then don't bother sharing it, because "they're the best servers because they have newer stuff". Very few people help the devs out so that code can make it's way into the master branch of the repo. If you want to use the old mail system, use an older client.

I mean exactly what i typed.. Your custom items should be in item_db2. When you pull the latest changes, you can just execute the item_db.sql file to make all the latest changes.

The item databases are designed to be "hot swappable". You can just run the item_db sql file and it'll reimplement any changes that have been made. You should keep your custom item data in item_db2. Any changes you've made to normal items should also be added to item_db2 so they're not overwritten when merging the latest item_dbs.

Yes, because it's a status symbol. That's exactly what we're moving away from. Unnecessary vanities.

Over the last few months, various changes have been made to the forum groups in an attempt to eliminate superfluous permissions and other changes that need to be made to groups when new content is created on the forums. This has been an immense help when setting up new sub-forums and Files categories, as we now don't need to double check permissions for 18 groups, we now only have to do it for 8. As these have been Staff groups, they didn't require a public announcement. The next two group changes do require an announcement, and at the very least a brief explanation for the change. Past Donators Originally this was just the Donators group, but the members of this group who had donated 3+ years ago were moved into a new group called "Past Donators". This was done to resolve an issue whereby members who actively donate and are automatically moved into the Donators group would receive the correct benefits, whereas a member who donated $10 in 2013 no longer qualifies for these benefits. This group change was made several months ago, and the final step of this will be completed this Sunday (19th March), whereby the group will be removed and all it's members will be moved back into the normal Members group. Community Contributors This group actually serves no purpose. A long time ago it was used to give recognition to members of the project that did something amazing, so they were rewarded with a group change. The CC group is also a sink for all Staff that retire from the project. Many members were moved into the CC group on rAthena based on their contributions/staff status at eAthena. The vast majority of members of this group no longer visit rAthena, so CC is a way of recognising members that are trustworthy, ex-staff, project contributors, etc. It's being replaced by badges to do the same thing. Retired Staff will receive the "Retired Staff" badge, and if a member of this group wasn't Staff at rAthena, they'll be given the special badge that best represents their contributions to the project. Why? Aside from the additional configurations per group when setting up new stuffs, it's a constant reminder of the past. A past that we're all moving on from.

Your msgstringtable doesn't match your client version.

4295

https://github.com/rathena/rathena/wiki/Clientinfo.xml To just give the yellow name, put the account id inside<yellow></yellow> tags.

npc/quests/the_sign_quest.txt

There are a large number of playtime/hourly points scripts that you can use with just a few edits to make it fit your requirements.

This sounds a lot like "i'm not allowed to talk about our services, but i'm going to anyway". Your level of customer service is what got your Paid Service listing removed in the first place. Pull the other one. I don't see much point in leaving this open for more replies that will undoubtedly be off-topic. Locked.

Paypal's IPN can't access 127.0.0.1, nor IPs behind firewalls. Instead of using Hamachi, you should try something like no-ip so your local networked machine can be visible from the outside world. That would require a slight change on your router though. The best thing to do would be to not host your server/website on a home computer.

IPN won't work with Hamachi IPs.

Inside your patch folder, have a .htaccess file that contains: Options -Indexes That will remove directory indexing so your patch files don't just appear as a list when your directory is visited... or simply put a blank index.htm file in there..

prontera,90,90,5 script Items 123,{ .@item = 501; // Red Potion .@qty = 1; mes "[Item Giver]"; if(itemgiver == 1) { mes "You have already claimed this item."; close; } mes "Here's an item for you!"; getitem .@item, .@qty; getitem = 1; close; } If you used the search function, you'd find lots of "Item Giver" scripts, some more complex than others.

Client side files have nothing to do with rAthena - you can use outdated files for your client and still use the latest rA git hashes perfectly fine. It all depends on what kind of server you're wanting to run.

"In this context" no one can really help you, you're using a while loop with a predetermined value that doesn't change. Remove the while clause before input and validate the data properly.