Jump to content

Akkarin

Forum Manager
  • Posts

    3,067
  • Joined

  • Last visited

  • Days Won

    182

Everything posted by Akkarin

  1. In an effort to aid the community, would you be able to update this thread saying where/how you found them so that this thread can help other users in the future.
  2. rAthena doesn't yet support 2020 clients. You use this is a base and use a 2018 or older client.
  3. But.. so is cron.. and you wouldn't need to install another package just to echo out the same code that you'd put into cron in the first place o.O
  4. Or upload it to the downloads area to benefit the community o.O
  5. No. He didn't say anything about extracting the data from the exe. He said find the msgstringtable.txt file in your translated data folder and edit the line there. It'll be with the other files you downloaded for english text that are probably sitting in your data folder.
  6. Akkarin

    PornRO

    Resurrected from some old files, the naked class sprites have returned. We're about to open for Closed Alpha and we're really excited to get things moving! Details: Pre-Renewal Mechanics using Renewal features. Episode 11.3 (rolling Morocc back was time consuming!) Our job class sprites are a combination of Default, Wearing Smalls (e.g. underwear/swimsuit) or Completely Naked! Full Installer weighing in at just over 1GB!! And things are about to get smutty. We've got some dirty events and instances cooked up with a variety of rather intriguing headgear and usable items! Needless to say, you need to be over a certain age to play this particular private server.
  7. Why are there two to do exactly the same job @[email protected]
  8. There's are several translation projects floating around. Realistically though, you'd be far better off translating the files yourself if you can as most translation projects (other than Zackdreaver's kRO -> English project) haven't been updated for quite some time.
  9. As i've already said, the error message tells you where to look for the erroneous code. There's absolutely no reason why you couldn't have fixed either of these issues yourself. It's all about the learning curve!
  10. Just turn if off in the chat options..
  11. This is not a forum issue so I've moved your topic into the appropriate location.
  12. I'm pretty sure i've read somewhere that the location of the broadcast displayed int he client window is hardcoded - you can only use the offset (fontY), but trying to duplicate the command will still use the same packets, so unless you're going to repack your client with new packets to handle this (which is not possible) then you're stuck with the announce code that everyone else has.
  13. The code is obviously not correct: 'UseMD5' => `false, Remove that erroneous ` The error literally told you where to look.
  14. The latest client date that rAthena supports is always listed as the default in https://github.com/rathena/rathena/blob/master/src/config/packets.hpp#L16 You can find that client floating around the Client Release forum. Also, please change your topic title to something more informative before I start handing out Warning Points. "lates clean hexed" could mean any client a few years down the road.
  15. Not without knowing which theme you're using, no.
  16. .... click "objects" in that dropdown list.
  17. There is absolutely no reason to resurrect a thread to tell someone that you've sent them a message. They'll see the message just fine without you telling them to go look for it.
  18. If it's a legitimate bug, posting it to Github would get the attention of our developers who can deal with it. https://github.com/rathena/rathena/issues
  19. You're resurrecting an old topic to ask a question that can be answered by simply reading the thread? Locking due to idiocy.
  20. Bugs should be posted to Github for the devs to see https://github.com/rathena/rathena/issues
  21. That's a hard one to answer. Technically it's possible to use a client that's more than 10 years old, but in all honesty, I wouldn't. An awful lot of code has changed since those old clients were supported, so if something breaks you wouldn't find much in the way of support from anyone, unless one of us oldies slide into your topic because we used to have a server back then and remember how they're set-up
  22. Instead of introducing spam into topics, why don't you do what someone else in this thread has already asked for and detail your setup, detail what you've tried, detail whether you're using Renewal or Pre-Renewal, your client date, your Git Hash, etc. We're not mind-readers.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.