KirieZ

It has been a long while since I last built one, and I never used WARP. But I think I can give you a few ideas...
 
All those errors are related to bad lua files. Maybe the way you generated them is giving bad results, maybe you have an issue loading them. I can't guide on the translation project as I only used it once or twice to mixed results, so I usually just build my client manually...
 
Here are some tips to try to debug these issues:
 
1. "attempt to call a nil value" means the function does not exists. Check if you have those LUAs and they have the required function
   - queryRegionInfo: data\lua files\seekparty\party_booking.lub or data\lua files\seekparty\party_booking_function.lub (I am not sure which one is loaded when, but I can see both has this function)
   - ResetTheHotKey: data\lua files\hotkey.lub
 
If you don't have these functions in those files, this is likely the cause. If you do, maybe you have an issue loading your GRF.
You can try tweaking how you generate your client from translation project and see if you get a better lua as output... just throwing ideas here as I don't know how to use it.
 
 
2. "attempt to index global 'JobSkillTab' (a nil value)"  as far as I remember, means some code is doing JobSkillTAb[IDX] while JobSkillTab is not initialized
 
Check if data/luafiles514/lua files/skillinfoz/skillinfo_f.lub is initializing a table: JobSkillTab = {} -- I think this is the root cause.
 
If it is not, your lua files are bad for this client
 
Hope this helps

as far as I know, not possible. Current clients no longer have the old character selection/creation window. the game simply moved on and no longer supports this. I don't think there is a NEMO patch for that, and creating one is likely to be quite hard.
 
If you really must use the old UI, you will need to go back to an older client

For the map, you are correct, you need the old map files since RO changed the academy several times.
 
I have uploaded the files here:
 
For a clean hercules, you should use Academy 2012 and start 2015 (2018 also works ok). I noticed that RE map cache is wrong for iz_ac02, so until this gets merged: https://github.com/HerculesWS/Hercules/pull/3316 you have to update your map cache for iz_ac02 for it to work properly.
 
About the combination kit, I think it is not implemented yet.

Hello everyone,
 
As you may already have seen from the 2024.03 release notes in GitHub ( https://github.com/HerculesWS/Hercules/releases/tag/v2024.03 ), Hercules' GitHub wiki has been moved to a new platform, powered by mkdocs and available at:
 
https://docs.herc.ws/
 
 
This change aims to make the Hercules documentation generally better since the mkdocs-powered documentation does bring a better navigation, search capabilities and editing options. With that we can, hopefully, cover the gap that many have felt after we switched from MediaWiki to GitHub Wiki, while also providing some extras (like the ability to easily have a local copy).
 
With the new mkdocs-powered document, we have: (compared to GH Wiki)
- A bit more control over the sections, no longer a single side bar with everything
- Extended markdown syntax for editing docs content
- Better searching, as results are shown as you type
- It is now possible to properly include image in the docs, without workarounds
 
Contributions are highly appreciated and should be made through Pull Requests to the new hercules-docs repository ( https://github.com/HerculesWS/hercules-docs ).
 
You may find general guidance on how to run the docs locally and edit it in the Editing the Docs page ( https://docs.herc.ws/contributing/editing-the-docs/ )

The content of the new repository was copied from the GitHub wiki (which was originally the MediaWiki content and had several contributions over the years), and reorganized into a few sections. Additionally, everything was converted to Markdown, so we should generally get an ok experience.
 
The conversion of MediaWiki pages to Markdown was made through an automated tool (pandoc) so we should still expect some things to not be perfectly right, a few noticeable cases are:
- Linking between pages are likely to be broken
- Some syntax highlighting may not be in the most presentable format
- Several images are still missing
 
Fixing those will require manual work to replicate the images, update links, etc.
 
Why not return to MediaWiki?
This question has shown up a few times in our Discord, and I think it is worth linking to the topic when the move happened back then:
 
TLDR; Maintaining MediaWiki together with IPB (our forum software) is complicated.
 
 
Huge thanks to Haru for making this idea come true!
 
Please let us know if you have questions, comments or suggestions for the new docs.

Yes, you are right about the cause.
 
Your case seems to be causing a similar effect of a server crash, when it gets terminated in an abnormal situation.
 
I am not sure if there is really something that can be done in this case... while you could create a script command to force saving the character data for this case, you would still have it open for others.
 
I think the best option would be to:
1. When doing a production server normal shutdown, always do it properly. Kick all players (even better: do something to prevent them from logging back in) and wait some time (I think ~5 minutes would be more than enough).
    I think if map server is shut down separately first, it will send all data to char, but this is something that would need to be done manually
2. If there was a server crash, which could cause those dupes, you probably need to either review your logs of the last few minutes and check if actions are needed, or rollback to a recent backup if you think it would be safer

That's weird... cvc was implemented together with the clan system, not having cvc would mean you don't have the clan system too. I do recommend updating though, since it is there since 2017. But here is the PR that introduced it: https://github.com/HerculesWS/Hercules/pull/1718
 

This seems somewhat undocumented, but there is a "cvc" mapflag that should make a clan vs clan. https://github.com/HerculesWS/Hercules/blob/stable/src/map/map.c#L5428
 
does that work for you? or there is a specific reason why you need to use gvg?

Is that from rA? does areamonster there sets this variable? this does not happen in herc: https://github.com/HerculesWS/Hercules/blob/stable/doc/script_commands.txt#L695
 
Ah, the answer went up and I didn't saw it 😅 Glad you got it working

It is in data/luafiles514/lua files/service_korea (_korea may be something else depending on how your client is patched and how your clientinfo looks like, but usually it is a country name)

Well, the short answer is: It depends.
 
But let's go for the long answer:
 
RO is a game that uses client/server model, and the server (in our case, Hercules) is the one which holds most of the game logic.
 
What this mean is, pretty much everything only happens in the game because the server tells the client to do so. To name a few examples:
- When you click to walk, Hercules is the one saying the client it can walk, and Hercules is the one letting other knows the player is walking
- A monster spawn only happens because Hercules is creating it and just letting the client knows the monster is there
- An attack (and a skill) only happens because Hercules calculated it and told the client that it happened
- A NPC is only shown in the screen because Hercules created it and told the client about its existence
- A Quest is received by the player because, for example, a NPC in Hercules added a quest to the player, and thus Hercules told the client about that
 
So, as you can see, pretty much everything requires something on Hercules side to work.
 
The client also plays some part on this:
- There are hardcoded limits of which IDs can be used
    - For example, an item which has an ID > 32k would only work on clients that supports IDs above 32k
    - Certain IDs for monsters/NPCs/etc won't be properly recognized in certain client versions
- There are some hardcoded logic on how skills works or shows up
   - For example, the old, ground-based effect of bard/dancer performances doesn't show in 2019 clients and newer (unless you use a patch to restore the old code in client). The ground effect would still happen (Because Hercules is controlling it), but the player would see nothing in the ground.
- UI elements are part of the client, so an older client may not have certain windows
   - But depending on the window, Hercules also needs to implement the network code to allow that window to work (e.g. Achievements, RoDEX, Equipment switch, etc)
 
Going back to your example about 4th jobs. Having a 2022 client means:
1. The visual effect for the 4th job skills are there
2. If the server says your job is one of the 4th jobs, you will see the sprite and it will be treated as a player sprite
3. You can see the new attributes window
4. You can see the new AP bar
 
But:
1. You don't have job change quests (Hercules must have the NPCs, which we don't as of April/2024)
2. You don't have a working skill tree and skills (Hercules must have the skill trees and skills coded, which we don't as of April/2024)
3. You don't have the effect of the new attributes being applied to your damage (Hercules must have new formulas for it, which we don't as of April/2024)
 
So:
Base client: kRO 2023 08 04
This means your resource files (sprites, luas, textures, maps, etc. the "visual" content and config files are from how kRO looked like in 2023-08-04).
 
For example, if a new hat is released in 2023-05, you will have the .spr file in your data.grf (but you can't get it in game if Hercules doesn't have it)
 
Client exe: 2022-04-06_Ragexe_1648707856
This means that your client will process client sided things as kRO did in 2022-04-06, this means it will be affected by client limitations from this date, and it will only load files that were expected at that time.

For example:
- if a new UI was released in 2023, you won't see it in a 2022 client, because the code was not there yet. (even if you have the images for that UI in your data.grf, you don't have the code to actually use them)
- if there is a new map format released in 2023 (map format meaning the structure of the files in the data.grf), this map file won't work here. On the other hand, if a map was released in 2023 using a structure that is compatible with a 2022 client, you can use it just fine.
 
Generally, having too different dates between Client exe and Base client may give you issues, because:
1. You have incompatible lua files (usually worked around by using translation projects)
2. You have new resources that are not compatible with your client (usually worked around by replacing the files or avoiding certain things)
 
 
Hercules: v2024.03
This is Hercules release date. This just means this is the state of Hercules code as of March/2024.
 
Hercules makes a new release every month, which may include bug fixes, new features, some custom code for something Hercules thinks is worth having, etc. You can see the changelog here: https://github.com/HerculesWS/Hercules/blob/stable/CHANGELOG.md
 
This date has pretty much nothing to do with the other 2. The only thing that it may suggest is that a 2018 Hercules will probably not work with a 2020 client, because we couldn't even imagine what 2020 client would look like when developing code in 2018.
 
But a 2024 Hercules doesn't mean it supports features from 2024 official servers, nor that a 2024 client would flawlessly work in Hercules. Currently, Hercules v2024.03 is a mix of content:
1. NPC/quest/job/monsters wise, I think we are around kRO 2015
2. Our client support is better, I think a 2022 client should work fine most of the time (some buttons won't work, though -- e.g. Equipment Switch is not there)
 
 
Hope this clarifies a bit

You are welcome
 
Regarding a roadmap, not really. We do track missing features and bugs in GitHub issues: https://github.com/HerculesWS/Hercules/issues
 
There are some milestones regarding content, but they are more for organization purposes, as we don't have a roadmap like "We are trying to get X done next"

Hello everyone,
 
As you may already have seen from the 2024.03 release notes in GitHub ( https://github.com/HerculesWS/Hercules/releases/tag/v2024.03 ), Hercules' GitHub wiki has been moved to a new platform, powered by mkdocs and available at:
 
https://docs.herc.ws/
 
 
This change aims to make the Hercules documentation generally better since the mkdocs-powered documentation does bring a better navigation, search capabilities and editing options. With that we can, hopefully, cover the gap that many have felt after we switched from MediaWiki to GitHub Wiki, while also providing some extras (like the ability to easily have a local copy).
 
With the new mkdocs-powered document, we have: (compared to GH Wiki)
- A bit more control over the sections, no longer a single side bar with everything
- Extended markdown syntax for editing docs content
- Better searching, as results are shown as you type
- It is now possible to properly include image in the docs, without workarounds
 
Contributions are highly appreciated and should be made through Pull Requests to the new hercules-docs repository ( https://github.com/HerculesWS/hercules-docs ).
 
You may find general guidance on how to run the docs locally and edit it in the Editing the Docs page ( https://docs.herc.ws/contributing/editing-the-docs/ )

The content of the new repository was copied from the GitHub wiki (which was originally the MediaWiki content and had several contributions over the years), and reorganized into a few sections. Additionally, everything was converted to Markdown, so we should generally get an ok experience.
 
The conversion of MediaWiki pages to Markdown was made through an automated tool (pandoc) so we should still expect some things to not be perfectly right, a few noticeable cases are:
- Linking between pages are likely to be broken
- Some syntax highlighting may not be in the most presentable format
- Several images are still missing
 
Fixing those will require manual work to replicate the images, update links, etc.
 
Why not return to MediaWiki?
This question has shown up a few times in our Discord, and I think it is worth linking to the topic when the move happened back then:
 
TLDR; Maintaining MediaWiki together with IPB (our forum software) is complicated.
 
 
Huge thanks to Haru for making this idea come true!
 
Please let us know if you have questions, comments or suggestions for the new docs.

Hello everyone,
 
As you may already have seen from the 2024.03 release notes in GitHub ( https://github.com/HerculesWS/Hercules/releases/tag/v2024.03 ), Hercules' GitHub wiki has been moved to a new platform, powered by mkdocs and available at:
 
https://docs.herc.ws/
 
 
This change aims to make the Hercules documentation generally better since the mkdocs-powered documentation does bring a better navigation, search capabilities and editing options. With that we can, hopefully, cover the gap that many have felt after we switched from MediaWiki to GitHub Wiki, while also providing some extras (like the ability to easily have a local copy).
 
With the new mkdocs-powered document, we have: (compared to GH Wiki)
- A bit more control over the sections, no longer a single side bar with everything
- Extended markdown syntax for editing docs content
- Better searching, as results are shown as you type
- It is now possible to properly include image in the docs, without workarounds
 
Contributions are highly appreciated and should be made through Pull Requests to the new hercules-docs repository ( https://github.com/HerculesWS/hercules-docs ).
 
You may find general guidance on how to run the docs locally and edit it in the Editing the Docs page ( https://docs.herc.ws/contributing/editing-the-docs/ )

The content of the new repository was copied from the GitHub wiki (which was originally the MediaWiki content and had several contributions over the years), and reorganized into a few sections. Additionally, everything was converted to Markdown, so we should generally get an ok experience.
 
The conversion of MediaWiki pages to Markdown was made through an automated tool (pandoc) so we should still expect some things to not be perfectly right, a few noticeable cases are:
- Linking between pages are likely to be broken
- Some syntax highlighting may not be in the most presentable format
- Several images are still missing
 
Fixing those will require manual work to replicate the images, update links, etc.
 
Why not return to MediaWiki?
This question has shown up a few times in our Discord, and I think it is worth linking to the topic when the move happened back then:
 
TLDR; Maintaining MediaWiki together with IPB (our forum software) is complicated.
 
 
Huge thanks to Haru for making this idea come true!
 
Please let us know if you have questions, comments or suggestions for the new docs.

Hello everyone,
 
As you may already have seen from the 2024.03 release notes in GitHub ( https://github.com/HerculesWS/Hercules/releases/tag/v2024.03 ), Hercules' GitHub wiki has been moved to a new platform, powered by mkdocs and available at:
 
https://docs.herc.ws/
 
 
This change aims to make the Hercules documentation generally better since the mkdocs-powered documentation does bring a better navigation, search capabilities and editing options. With that we can, hopefully, cover the gap that many have felt after we switched from MediaWiki to GitHub Wiki, while also providing some extras (like the ability to easily have a local copy).
 
With the new mkdocs-powered document, we have: (compared to GH Wiki)
- A bit more control over the sections, no longer a single side bar with everything
- Extended markdown syntax for editing docs content
- Better searching, as results are shown as you type
- It is now possible to properly include image in the docs, without workarounds
 
Contributions are highly appreciated and should be made through Pull Requests to the new hercules-docs repository ( https://github.com/HerculesWS/hercules-docs ).
 
You may find general guidance on how to run the docs locally and edit it in the Editing the Docs page ( https://docs.herc.ws/contributing/editing-the-docs/ )

The content of the new repository was copied from the GitHub wiki (which was originally the MediaWiki content and had several contributions over the years), and reorganized into a few sections. Additionally, everything was converted to Markdown, so we should generally get an ok experience.
 
The conversion of MediaWiki pages to Markdown was made through an automated tool (pandoc) so we should still expect some things to not be perfectly right, a few noticeable cases are:
- Linking between pages are likely to be broken
- Some syntax highlighting may not be in the most presentable format
- Several images are still missing
 
Fixing those will require manual work to replicate the images, update links, etc.
 
Why not return to MediaWiki?
This question has shown up a few times in our Discord, and I think it is worth linking to the topic when the move happened back then:
 
TLDR; Maintaining MediaWiki together with IPB (our forum software) is complicated.
 
 
Huge thanks to Haru for making this idea come true!
 
Please let us know if you have questions, comments or suggestions for the new docs.

I think clients from 2019 and up supports up to ID 2 billion, even for costumes.
 
I am not sure which client you are using, but newer clients should be the only real option.

View File jRO Exclusive Monsters
All jRO Exclusive, Event and Special Episode monsters.
This file was originally posted by @fxfreitas at Midgard-Community.
 
The archive contains the following monster sprites:
abyss_arthur (corridor of abyss special instance boss) AMELIT (ghost carring a gemstone) ANGLERFISH (Mini-boss) CHAOS_DEVIL_DRAGON deviruchi_w (a white deviruchi, event) domovoi (custom pet, based on RO2 domovoi) ECHIDNA EMELIT (ghost carring a gemstone) giant_deviruchi (event monster) giant_deviruchi_w (event monster) headless_mule (remake of original brasilis monster, last kRO already implemented) HERA (Episode Monster) j_taini (tiny, event monster and pet) kraken_baby (marse edit) LILITH (Episode Monster) M_DARK_KNIGHT (Mercenary monster) M_FLAME_KNIGHT (Mercenary monster) M_ICE_KNIGHT (Mercenary monster) M_LIGHT_KNIGHT (Mercenary monster) M_STONE_KNIGHT (Mercenary monster) merman_se (merman edit) METAL_DRAGON (Pet and dungeon monster) MYTHLIT (ghost carring a gemstone) pad_fafnir (Can't Move, Can't Attack) pad_helheim (Can't Move, Can't Attack) pad_horai (Can't Move, Can't Attack) pad_ifrit (Can't Move, Can't Attack) pad_kinggold (Can't Move, Can't Attack) pad_kingmetal (Can't Move, Can't Attack) pad_leviathan (Can't Move, Can't Attack) pad_muspelheim (Can't Move, Can't Attack) pad_mythlit (Can't Move, Can't Attack) pad_niraikanai (Can't Move, Can't Attack) pad_shangrila (Can't Move, Can't Attack) pad_tamadora (Pet) pad_zaerog (Can't Move, Can't Attack) pad_zerog (Can't Move, Can't Attack) poseidon (strouf edit) RUBYLIT (ghost carring a gemstone) SAPPHLIT (ghost carring a gemstone) seiren (obeaune edit) SIREN (Episode Monster) tacnu (Mini-boss) TOPALIT (ghost carring a gemstone) Submitter Kenpachi Submitted 04/22/20 Category Sprites & Palettes  

The team at Hercules wishes you peace, joy and prosperity throughout the coming year. Thank you for your continued support and contributions. 
We are here, because each member of our boards is proud to be part of it. I really look forward to see what 2020 will bring us.
 
Relax and enjoy your well-earned free time as much as possible, We wish you and your family a Merry Christmas and a Happy New Year!
Thank you,
Ridley

It looks like your db is missing some parts, are you using the sql files from your emulator? Try recreating your database

If you are sure that you have all the updates, I think you can run the queries that insert entries in the sql_updates table: https://github.com/HerculesWS/Hercules/blob/stable/sql-files/main.sql#L876

Touch-motions supported
Very usefull update, I started to interest myself to mobile specific features.
Now, Android is officially supported and here are described touch motions I implemented to navigate in game.
I tried to be as intuitive as possible, inspired by Google Map gestures :
Zoom : Spread fingers Perspective : Go up/down fingers Rotation : Inverted fingers Reset : Double tap It gives an immersive experience and prepare future updates for mobile client version.

July Digest 2019
The following digest covers the month of July 1st - July 31th 2019

Team Changes
None Added
Added/updated packets, encryption keys and message tables for clients up to 2019-07-24. (#2498) Added a setting to have `@autoloot` take player drop penalties/bonuses into account. See `autoloot_adjust` in `drops.conf` for details. (#2505) Added a mob DB field `DamageTakenRate` to change the rate of the damage received by each monster. (#2510) Added a setting to allow homunculi to obtain a portion of the EXP gained by their master. See `hom_bonus_exp_from_master` in `homunc.conf`. Note: in order to restore the previous behavior, the setting can be changed to `0`. (#2507, issue #2313)
  Changed
Converted various packets (`ZC_ACK_RANKING`, `ZC_STATUS_CHANGE_ACK`, `ZC_HAT_EFFECT`) into structs. (part of #2498) Changed `pc_statusup()` to send the actual stat value back to the client in case of error. (part of #2498) Disabled the `@refresh` and `@refreshall` commands during NPC conversations, causing the character to be stuck on an invisible NPC dialog until relogging. (#2499) Extended `@reloadmobdb` to update the currently spawned monsters. (#2500) Changed the party sharing checks to avoid unnecessary SQL queries. (part of #2502) Extended the `@refine` command with shortcuts to refine every normal equipment (-1), every costume equipment (-2) or every shadow equipment (-3). (#2504) Extended the `@refine` command to list the costume and shadow equipments. (#part of #2504)
Increased the stack limit of Turisus, Asir and Pertz to unlimited and the other runestones to 60. (#2509) Extended the commands `getmonsterinfo()` and `setunitdata()` / `getunitdata()` with accessors for the new `DamageTakenRate` mob DB field, using, respectively, `MOB_DMG_TAKEN_RATE` and `UDT_DAMAGE_TAKEN_RATE`. (part of #2510) Converted the Guild Castle database to the libconfig format, in preparation for future updates. (#2506)
  Fixed
Sanitized the use of `input()` in all the scripts to work correctly if the minimum accepted value is changed to less than zero in the configuration. It's recommended that third party scripts get updated not to assume a positive value, since the default setting may change in the future. (#2494) Fixed an issue in the Sealed Shrine script, allowing to unseal multiple Baphomets under certain conditions. (#2332) Fixed an issue that allowed an appropriately created party to enable experience sharing even if outside the sharing range. (#2502) Corrected the cooldown after killing Wounded Morroc. (#2503) Corrected `isequipped()` and `isequippedcnt()` to correctly handle costume equipment. (#2508)
  Deprecated
None  
Special thanks to
@Haru @4144 @Asheraf @Emistry @KirieZ 

IIRC Item stat enchants basically add a "card item" into the 4th slot (which enchantable items doesn't have for cards), and that item looks like an sphere. It is an item, you can find it on item db (look for Int_3 or something like that).
You can probably change the sprite if you want, just like you do for any other item. But in this case it looks more like yourdata. grf is out of date... does other enchants work fine? I may be wrong, but this is what I remember...
ItemInfo.lua and .lub are "the same" (actually .lub would be the "compiled" version of .lua, but a lot of time we use it in plaintext)

It should be exactly like adding any item. You have to put the .spr file in the sprite directory as you did and also the item and collection bmp in texture folder. Iirc they are:
texture/À¯ÀúÀÎÅÍÆäÀ̽º/item/<item name>.bmp  --> the sprite that appears in yor inventory
texture/À¯ÀúÀÎÅÍÆäÀ̽º/collection/<item name>.bmp  --> the image that appears when you right click
 

Hmm yes, I think you should duplicate original card act and rename to taogunka.act. You need to get it from official data.grf, it is probably at:
data/sprite/¾ÆÀÌÅÛ/À̸§¾ø´ÂÄ«µå.act

https://gitlab.com/4144/Nemo/blob/70f27fe5c114f7c7f834f95f6ab0e8decf8dc6af/ChangeLog.md
New patches:
Increase hair style limit in game (old) - contains old patch for extend hair sprites id for human.
Force use icons only from stateiconimginfo.lub by Jchcc.
Add patches for hide all other buttons by 4144.
Add patches for set hide/show other buttons by 4144.
Allow spam skills by hotkey by Functor, 4144.
 
Updates patches:
Increase hair style limit in game - now extending hairs for humans and dorams.
 
New translations:
Add Thai translation by Kelberwitz Blade's - found packed nemo archive in github.
 
Plugin updates:
Show client version always with UTC time zone.