Akkarin

Perhaps one of the graphics talents may still have this; it looks like it could be Usako's? @Chemical Crush @Najara @Adel @Haziel

If anyone has thought about submitting their application in the past but didn't, now is an ideal time! We are in need of additional Content Moderators

This is not currently part of rAthena and is not a simple script, it's an overhaul of the refinement mechanics. The devs have it on their list of things to do.

I think the error kinda speaks for itself.

Over the last few months there has been a significant drop in donations (4 donations since March), so some of our staff have been paying our monthly running costs as well as developing awesomeness for your servers. So, in an effort to keep our forums running on great hardware and to finally (hopefully) give us the opportunity to send some of the donation funds to our wonderful developers, they have come up with an idea; Development Donation Goals will allow them to release new features while helping to keep our forums running, and eventually lead to them getting some well-deserved cash for their efforts to support you all, which they've been doing for free for many many years with little to no recognition. The concept is simple. On the Donations page along with the normal "Donate to rAthena" button there will now be "Development Goals" for specific features. I'll also add this to the right-hand module area on the board index. Once the target has been met, the devs will release that particular feature. None of our developers have ever been a fan of individual devs selling features or code that would benefit the entire community, as that's not the aim of an open-source project, so I'm supporting them fully with this decision. Every little helps! P.S. You can also use your account credit towards donation goals by sending me a PM and describing how much of your credit you would like applying to which donation goal. Credit donations are converted at a ratio of 2:1.

Correct - if we're gathering the data ourselves, everything is generally written from scratch. If we have an official file then we run it through a script converter to change the syntax and then spend ~3 hours reading line by line to double-check.

Scripts are converted by looking at the original Aegis file for the script, then rewriting it in our scripting language. When official files are unavailable (there haven't been any decent leaks for years) the devs play through the scripts on official servers while taking screenshots for dialogue or using tools like wireshark to capture text for translating. There are many guides on the internet detailing packet analysis.

The link clearly explains what you need to do.

https://github.com/rathena/FluxCP/blob/master/doc/user_theme.md

We can't help you with your Paypal issues - speak to them instead.

"/showname"

Since half-working code is in this thread and not in the main repo, it might be an idea to throw it into a pull request so others with the knowledge can contribute and get code pushed faster.

Stop arguing each other's meanings. We don't have full support for RoDEX yet on the later clients, but it will be coming soon. This means we won't entertain support issues/requests regarding RoDEX on the newest clients.. since.. it was already announced that it won't work fully.

There's no need for an excessive use of caps. This also clearly isn't a forum issue, so posting this topic in Forum Issues was obviously the wrong place. Topic moved.

Also, post in the correct section. This is clearly not an issue with our forums, so it shouldn't have been posted under Forum Issues. Topic moved.

Moved from Forum Issues to database support.

Github has a search feature too, along with commit history and blame functionality per-file. I typed bSubSkill into the search box, then noted the line number, then hit "Blame" and scrolled down back to the line and it shows the last commit that touched that particular line, which was indeed the commit that introduced the bonus: Git Hash: 549f491

If you guys were a little more patient you wouldn't need to do anything in order to get the 2017 clients working. The devs are working on building support for the newer clients into rA.

I think you're expecting a client shield to do more than just protect your game client. Gepard just stops the client from doing something else.

Ensure you're using the correct KR encoding. If you're using utf8 it'll convert the characters into something else, then when you save it, the client won't recognise and you'll get string buf errors.

Welcome back Z3R0! The RO Emu world has felt a little emptier with your absence

It'll be in the etcinfo.txt file in data.grf. You can just overwrite it with your own. Updated to 2017-06-07, now includes the new version of RSU by Ai4rei so HTTP patching works.

The size is hard coded into the client.

It might also be worth using a public repo on github so people who have already made changes to roBrowser can create pull requests. There's a fair few of us that use roBrowser for various things and so so many of us have already added some of the missing features.