Akkarin

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.

I assume you had installed a valid SSL certificate and that HTTPS traffic was enabled correctly? Non-SSL subdomain may well be the way to go.

Latest GIT compiles fine. Check that things you've added previously work with later implementations.

Like i said, they're designed specific to a project, so it's likely that a project like this would have their own person who designs their maps. There are a few individuals left around that create maps - you might be able to find a few in the Third-Party Services page, or on facebook, or via google.

Maps with this level of detail? No. They're generally made custom to a particular project.

I would imagine their GRF has it - if it's encrypted then they purchased it from somewhere or made it themselves and don't want it to stolen/redistributed.

You can't selectively choose to use SSL only on certain pages without changing a bunch of stuff. Thor has worked fine using https for many people - if you're struggling you could just use a non-SSL'd subdomain?

Yes. Install an SSL certificate.

It's called Third-Party Services - there's an announcement about it and a link under "Community" in the navigation bar.

rAthena doesn't implement changes based on episode, they're based on whatever information we can obtain at the time so that list will be all over the place. It's virtually impossible for a team of volunteers to produce a timeline when they have new features and bugs to fix at the same time. Life issues, along with whether or not they even feel in the mood to do anything RO related are big factors when we have a small team.

Turn off debug and visit the URL of the base robrowser directory, not the client folder.