Leaderboard

Need the latest kRO Install folder for your private server? Look no further! ----> Download <---- Latest: 2023-04-04 Installation: Official kRO Updated: 04/04/2023 Download Link: https://mega.nz/folder/jUsDgRxQ#ttLmLjPY9p9cfU5_ShWVCw Package contains RSU RO Patcher Lite for kRO and kRO RE by [Ai4rei] This package is maintained by [Akkarin] Note: Due to continued abuse of my webservers, the files have been moved to MEGA. You can download an extractable .zip of an installed kRO directory, or you can download the official installer from kRO's website. Note: If you require older maps that are compatible with 2021 and older clients, download the 2021 .zip. A fan of this topic? Hit the rep button

Hey all, so I downloaded the pre-configured 586, 620, and 2.0 from the Browedit discord links, and I'm having trouble opening maps (e.g., prt_fld_01) from my data.grf. At first 586 and 620 would just close the entire program whenI tried to "open from .grf" I then ran 586 and 620 in compatibility mode (i'm on win10) and it would open a blank map with one yellow dot. Browedit 2.0 gave me an error that looks the attached image. I also checked that my .grf is under 2.x gigs and it's only 1.4g. I get a bunch of errors that looks like "Error: [22:13:43] Error loading texture C:\......clientdata\texture\┐÷┼═\water000.jpg! gd-jpeg: JPEG library reports unrecoverable error: Not a JPEG file: starts with 0x00 0x00 What's going on here?

https://www.mediafire.com/file/z5hkpzfk59emkls/LocalClient_%281%29.apk/file version 315 APK

Hmm this also works for me. I tried vs. Medusa and with Evil Druid Card or Medusa Card, I never get petrified. The code is also in place in status.cpp: case SC_STONE: case SC_STONEWAIT: case SC_FREEZE: // Undead are immune to Freeze/Stone if (undead_flag && !(flag&SCSTART_NOAVOID)) return 0; break; You could debug there and check why it doesn't reach the "return 0" part in your test case. For Medusa Card the could would be in status_get_sc_def: // Item resistance (only applies to rate%) if (sd) { for (const auto &it : sd->reseff) { if (it.id == type) rate -= rate * it.val / 10000; } if (sd->sc.data[SC_COMMONSC_RESIST] && SC_COMMON_MIN <= type && type <= SC_COMMON_MAX) rate -= rate*sd->sc.data[SC_COMMONSC_RESIST]->val1/100; } Note: That if you set undead_detect_type to "race", then of course Evil Druid Card doesn't protect you from Stone (has nothing to do with mobs, though). Medusa card would work either way.

I've used this guide twice and it always works for me. It's great, but needs a few updates. 1) yum -y install devtoolset-4-gcc-c++ This is outdated and won't work. You need to use this first: sudo yum-config-manager --enable centos-sclo-rh-testing If yum-config-manager returns command not found, you need to yum install that first. And then it will work. 2) Enter the name and switch Type to Linux and Version to Red Hat (64-bit) and click in Next. If the dropdown menu does not have 64 bit versions available, it means one of two thing: Your CPU does not support virtualization, or it does support it but the option is disabled. You need to enable it on the BIOS. Processors made by AMD will always have the option(mine was disabled by default) while on Intel chips sometimes do not. 3) It's always a struggle for me to get internet working on the VM the first time you set it up. A little bit of Google-fu goes a long way but I usually end up having to edit some network files to get it to work. Also apparently not every wireless router allows Bridged Adapter mode to function. 4) This guide DOES WORK for Dynamic IP addresses without problems. The issue is that every time your dynamic IP shifts, you'll have to edit your local server files with the new IP. I've hosted servers with dozens of people connected for weeks this way, just hope there isn't a lightning strike near your home that causes the lights to flicker(and the modem to reset).

Problem solved. Neither of the major 2 data files from this link are compatible with Borf's editor. One is too large, and the other doesn't work (see below). I had to download the 2017 data.grf from here. So far everything is working fine. Best guess is that those "unnecessary files" they removed to make the .grf smaller were, in fact, quite necessary...