Jump to content


  • Content Count

  • Avg. Content Per Day

  • Joined

  • Last visited

  • Days Won


Ai4rei last won the day on November 29 2020

Ai4rei had the most liked content!

Community Reputation

313 Excellent

About Ai4rei

  • Rank
  • Birthday 01/04/1912

Profile Information

  • Gender
    Not Telling
  • Location
    Czech Republic
  • Server
  • Github: ai4rei
  • Discord: Ai4rei#2197

Contact Methods

Recent Profile Visitors

16,644 profile views
  1. Updated to 4.0.1, this release fixes, among others, an issue that prevented updating jRO RAG (thx to @legendx for reporting), when there are more than one year worth of patches to apply. -- This should fix your problem @legendx and @napasaro.
  2. If you could provide all of the problem details, it would be good. If you cannot recreate it, it should be recorded in the Event Log (Application category, Appcrash Event) as well. For now I only see, that the 32-bit patcher tripped a should never happen guarded scenario.
  3. Works for me™. Try recreating the folder and/or check security permission of that folder (at least read/write current directory). From the screenshot it does not look like you use Windows 10, so there is probably no defender to interfere, but if you use an AV software, try disabling that temporarily to see, if that helps. Report back whether that helped or if a follow up is needed.
  4. What is the path to the patcher? Like C:\RO\...
  5. As stated before, a GRF is needed. The patcher will not attempt to create a GRF if it is missing or otherwise invisible. In this non-standard scenario you have to create a zero length data.grf to fool the patcher into thinking, that it just created the GRF. This may sound like a bug, but has been a feature since v2.0, though in the past the patcher created the GRF without nagging. The main reason for the change was, that if you are sharing one data.grf between multiple RO servers, each in a different folder, you may forget to return the GRF back before patching and end up with something incomplete. Basically it makes you aware, that you misplaced the GRF and should look for it before you start patching it. It's a patcher after all, not a GRF tool. TL;DR: If there is no GRF, patcher will not work. If you do not have one, make a zero-length GRF.
  6. The provided source is not complete (thus for reference only). The latest commits were preparation work for the ROCred+RSU merge, so please wait for that. There won't be further stand-alone ROCred releases.
  7. 2010-07-30RE is broken, use 2010-07-28RE or 2010-08-04RE. RO OpenSetup This will tell you, if there is something wrong with your RO folder in regard to setup. If there are no resolutions to choose from, make sure: Your graphics card drivers are installed (Microsoft Basic Display Adapter is not a proper driver) No mirror driver is running (ex. VNC/RDP server) If it still does not work, you can try providing the output of this or that.
  8. At least an empty grf file, though why would you use the patcher without files?
  9. Updated to 4.0.0, this major release contains a refreshed UI, completely reworked GRF engine, native 64-bit builds and other, far too many under-the-hood changes and bug fixes to mention them all, see included doc/history.txt for details.
  10. That differs by server, even on official, sometimes significantly. Doing find/grep on your npc folder is probably all you need.
  11. For various reasons an idea came up, to have a reverse search (or search-by-image) function in the NPC list. The question is, would there be general demand for such a function, or not?
  12. Sakray data too old, only clients from 2018+ are supported. Older clients will be only supported, if someone provides a mirror server for that.
  13. Ai4rei

    How to fix this?

    Àΰ£Á·\¼ºÁ÷ÀÚ\¼ºÁ÷ÀÚ_³²_´Ü°Ë_°Ë±¤.act Hair style has nothing to do with that. The missing file corresponds to a male (남/³²) acolyte (성직자/¼ºÁ÷ÀÚ) with a dagger-type weapon (단검/´Ü°Ë). Acolyte classes generally do not wear knifes or daggers, so this resource does not exist in regular data. Changing jobs should un-equip all equipment to prevent this sort of errors, but for some reason, it did not in your case. Edit: Just noticed, this thread is pretty old.
  14. Create a thread in a DLL, that displays a topmost window with a bitmap in it and close it when the main window is created (which can be detected in various ways, for example polling with FindWindow). That DLL must be added to client's imports (or recycle an existing one if you know how). Edit: For example like this: https://github.com/ai4rei/splash
  15. Updated to 2.14.2, adds /mable and /zoom, updates Japanese and Russian translation and fixes UI glitches and a bug in logging.
  • Create New...

Important Information

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