Gouki

Hi Guys, Have anyone encountered this issue before? I'm still currently backtracking my updates but, this suddenly popped up and is unable to be closed. When you click the top left (encircled in red) message log settings pops up.

Hi All, Wondering if its as easy to create a cuustom item_group_db. Im planning to use it on a custom lapine synthesis group. apparently adding it to item_group_db doesn't recognize it. Tried searching into forums and doc, and not sure if I need to add it to const.yml, or do an SRC update in script_constants.hpp?

Found the issue, it's about Chat Alliance command being not available on my SRC. Had to remap the Charcommand identifier via conf. and install chat alliance src to fix the issue. This may be closed. thanks!

GDB didn't print any as maybe because the server didn't really crash. GDB didn't print any.

there are quite some commands being added already for sometime now, unfortunately this charcommand was not tested since its on dev phase. do you think added commands affected it? Could there be other options to check as to why this happens?

Are you referring to #define packetver of src/config/packets.hpp?

Hi Guys, Been wondering why my charcommands (#item, #zeny, etc) are not working. It instantly disconnects the account from the client and shows a warning in console. Mapserver does not crash, you can log back in right away. The account group set on DB is 99. groups.yml settings is in default, which I think by default 99 - admin level should have permission to it. Could anyone enlighten me is this is a client diff / SRC / setting issue?

Well, everyone started as a noob in server creating. we all learn by the process and you should be eager to learn. Honestly, there are lots of materials/tutorials already, here in the forum and in youtube that you can follow step by step. Chris translation has its own youtube channel where he explains how to use the tool to create a clean data file, prerenewal included. very helpful. unlike when we started we all have to merge files and translations to get what we like. I can't give you a straight answer on how to do things, but learning by yourself with the help of the forum will teach you alot of things and you'll understand better than just following what people will tell you to do. When you choose a client, you should update your src packets as well and compile to the client date. this is for it to work.

The current client date pre setup in rAthena is 2021-11-03, so I'd recommend the same. Another famous client for Pre-renewal is 20180620, however if you use more robe costumes, it wont look good as 2021. I believe this depend on the goal you are trying to set as a pre-renewal server, definitely there are some client bug fixes along the way. But most significant changes here is the feel of the client, the older the client, the lesser the features it will provide. so again it will lead to the goal of the server you are recreating. Pre-renewal but with newer features 2021. Pre-renewal in general 2018. Totally pre-renewal, maybe you can go as far as 2015 client. Just be cautious since if you use older client, there might be packet/compatibility issues as well, if you'll use the latest rAthena.

@Playtester Hi this works wonders, thank you so much! I have a concern now with regards item defenses. I'll drop you a message instead to avoid leading this topic to a different discussion. thanks!

I checked, it does not affect equipment attributes tab. see sample below

I think thats what happened, language of GRF editor broke the ANSI encoding. The items were fixed already, what I did was I created a new blank GRF and set it initially to ANSI before adding my files. then just saved it as GRF. I did a GRF diet on my files, not sure if that caused the issue. Nonetheless fixed now. Topic may be closed.

Hi All, Tried editing item_db but it only affects the status window (alt+a), it doesn't update the equipment attributes tab. wondering where is this being recorded?

Client date is 20240902 I'm using the most recent ROenglishTranslation by Chris I did try to use the original kRO now and apparently, issue seems the same. UPDATE: seems to be working now, just reverted back everything, GRF seems to be the issue.

I initially checked this also, and yes it is a match...