This is kRO. You use this package as a base for creating your private server's client files. Add your diff'd client, and a translated data folder for it to work with your server.
The files and imports are generated automatically after you've compiled rAthena for the first time. You don't need to create any extra files or add in the import: lines manually. It's already done for you ?
Yes, but also no.
You can run another program while the patcher is open, which will give you the two clients capabilities, but the patcher will stay open until you close it.. which you've already tried.
I think there's an old @command somewhere that does the same thing - so in your equip & unequip scripts you would have something similar to:
{},{ headvar=getlook(LOOK_HEAD_BOTTOM); changelook LOOK_HEAD_BOTTOM, 2231; },{ changelook LOOK_HEAD_BOTTOM, headvar; }
Why do you need a separate client? Add an extra set of connection info's to the clientinfo.xml file, or join both char servers to the same login server and then you don't need two separate clients with two separate lots of data files.
If XPRO is web-based (with apparent apk files for mobile) though pretty-much built on roBrowser's source, but you have to pay for a license to use it. roBrowser has always been intended to be open-source. Vykimo could've just continued work on roBrowser instead of being money hungry. There are other roBrowser continuations where many of the newer features have been added in separate forks. I myself use rAthena and roBrowser in a completely different context and host an online gardening game with it. If you understand javascript, it's actually not that difficult to implement the features that are missing.
Well.. your error literally tells you what's wrong. I also won't be supporting Hercules script mix-ins. I literally replied with the same statement in the thread you linked. rAthena has different functions to Hercules, you should check on your mapserver what the errors are and then cross-reference with the doc/script_commands.txt file to see what's going on.
??
It doesn't require a client, it is the client.
It works fine if you don't need carts, vending, half the skills, rodex, quests, achievements, homuns/mercs, etc.
// Log MVP Monster Drops (Note 1)
// Outdated. Use Pick_Log instead. But this log could be useful to keep track slayed MVPs
log_mvpdrop: no
I assume you set this to "yes"?
I do wish you guys would stop calling it an "offline" server. If a server is "offline" then it doesn't work. It's down. It's off. Hence "offline".
It's called a local server.
Simple answer: You can't.
Long answer: You will need to dig around in old scripts and previous versions of files using the Git History and Blame feature in order to get the scripts back to an old enough version and then apply any fixes manually. Literally no one will spend 50+ hours doing this for you.
As far as i'm aware, rAthena doesn't support any 2020 clients. This package is a good base for your client-side folder, but you'll need to use a supported client to diff and then a translated data folder.
It's using a global variable set from each kill by any player. It's total kills from all players.
I'm afraid I don't know anything about big HP bars. Though if you mean like for greater effect you could use cutins and update them after each % is reduced.
Content and features are slightly different. Feature-wise we're around the 16.1 mark, content-wise we're still gathering data to update our databases for 15.2 (devs please correct me if i'm wrong). There's an awful lot of data flying around that we could use to half-update some of our databases, but then they wouldn't coincide with other areas where we have data to publish for 16.2 or even the newer 17.1 data. The item and mob db can be updated to match kRO on the fly, but making sure that other systems and features work cohesively is what keeps us behind, because we can't simply push out updates for things that the emu isn't ready to handle.