Jump to content

Linus

Freelancer
  • Posts

    211
  • Joined

  • Last visited

  • Days Won

    18

Posts posted by Linus

  1. The patcher stores the ID of the last patch in jRO.inf. When you run the patcher, it compares the ID in that file against the ID on our webserver to see how many patches it needs to download, if any. After patching is completed, it saves its progress in that file.

     

    If you copied the jdata.grf from another computer, please copy the jRO.inf from that computer as well. This will ensure that you're not re-downloading patches that you don't need, or risk messing up your jdata.grf by accidentally downloading patches that have since been removed.

     

    Happy to help.

  2. Gepard Shield is attached to the server's IP address and ports, so when we did the recent migration we had to temporarily disable gepard shield because the new server has a different IP address assigned to it.

     

    I'm not sure why you have a jdata.gpf as those are patch files, but the issue is not with jdata.grf. Gepard is attached to the client (jRO.exe), when we moved to the new server, we sent a client without Gepard shield over the patcher. If you see the Gepard splash screen when you run the jRO.exe then you never received that patch. Please send me a PM or message me on Discord and I'll help you out.

  3. There are two files in the zip, gepard.grf and gepard.inf. The inf is used to store the last patch that was downloaded, so the patcher where to start patching from. You need to copy BOTH files from the zip, not just the grf, otherwise your patcher will keep trying to download the grf over and over again.

  4. The file in question is a patch released by us, not kRO. The link you posted is for kRO's patch server, you won't find any of our patches on there. We host our own patches, but the FTP directory is password protected to prevent other private servers from easily stealing any content and extracting it for their personal use.

     

    I renamed jRO.inf and jdata.grf forcing the patcher to redownload everything, and I was able to patch successfully without any errors. This verifies that file does indeed patch. I have not heard of any other patching issues. Please try to do the same and report back.

  5. From what I've been reading, kRO's patch servers have been updated to block more IP ranges to attempt to prevent patching for private servers. There are patchers that have been updated to bypass this, but the developer has not updated the patcher we use yet. In the meantime, you can download the "RO Patcher Lite for kRO" and "kRO Patcher Lite for kRO RE" place them in your JellyRO folder and run them manually. These should be able to patch kRO, then you should be able to start the game normally.

  6. The support ticket module is a plugin for the control panel we use and is not very well written or updated on a regular basis. As a result, we are experiencing some issues with it. Regardless of not being displayed, any tickets you submit have gone through, you can verify this by logging into the old control panel at www.jellyro.com/cp_old/. Despite our current small population, we receive numerous support tickets per day and have a small staff who each excel at different areas, thus the tickets have to be assigned based on who is able to complete it and that person's workload. So tickets may not receive the immediate attention that you get in-game from using @request but rest assured, they will be answered.

    • Like 1
  7. @Logy - Open your hosts file (C:\Windows\System32\drivers\etc) with Notepad and add the following line at the bottom

    112.175.128.134      webpatch.ragnarok.co.kr      #kRO Patch servers

    Then try running the patcher again and see if it patches.

  8. Opening ports will not help anything in this scenario. Try seeing if this loads. Since your computer can't resolve the domain name to an IP address, let's see if it'll load using the IP address instead of the domain name. If you are able to see the link above, then that tells me there's something wrong with your DNS server, but there's a simple work around that will let you get start patching again.

  9. We need to determine whether you're being blocked by something on your computer, your internet provider, or kRO's server. Please open a command prompt and type the following:

    tracert webpatch.ragnarok.co.kr > C:\tracert.txt

    This will display every step along the route that it takes to get to kROs servers and how long each step takes. By figuring out where it stops, we should be able to determine what is blocking you and how to fix it.

    It will take a few minutes to run, you'll know it's done when you can type in the command prompt again. After it's done, open C:\tracert.txt and paste the results in here.

  10. When was the most recent time that this occurred?

    How often does this occur?

    What time(s) are you normally logging on, in relation to server time?

    How soon after logging in do you experience the disconnection?

    Do you have any programs running (Torrents, Usegroups, Peer to peer file sharing programs, etc) that may be making the hogging bandwidth (not necessarily on the same machine)?

  11. Simple answer is no. The list of available resolutions in the anesissetup.exe program is based on what your graphics card and connection (VGA, DVI, HDMI, DisplayPort) are able to support. You can try downloading the latest drivers from the manufacturer and see if it improves any, but it's likely that it won't. If you are on a desktop you can invest in a better graphics card, most laptops have an onboard graphics card and can't be upgraded or replaced.

  12. Okay, I did it and I got the same message :/

    Our patcher downloads in the following order: kRO, Renewal, Anesis. If you're getting the same error message on both patchers, this tells me there's something restricting you from accessing the kRO patches. Please see if you can access either of the two following sites...

    kRO patch list

    Renewal patch list

     

    I can't patch either, my RO folder doesn't have the patch_allow (and I tried with the antivirus and firewall off, while running the patcher as admin, didn't work).

    The patch_allow.txt is downloaded every time the patcher runs and deleted when the patcher closes, these files do not remain on your computer. See if you can access the sites above.

     

    Failed to open Data.grf what is this?

     

    Never mind its working now.

    This happens when you run the patcher while a client is running. Please make sure there are no active clients before attempting to patch.

×
×
  • Create New...