Enable reading TXT version item_db

[Keitenai]

Hello,

A lot of rAthena users preferred to use text database, and I am one of these users since it is so much easier to trace | modify | compare.
I've been trying to find a workaround to enable rAthena to still read text version of item database, but frustratingly I don't have the knowledge & capability to do so.

 

I really hope that there would be someone out there who can help in making rAthena be able to read text version of item db.

 

Please hit like if you are like me who prefer to use text version item db.

Thank you!

[Troll]

YML is more readable and friendly (EASY TO ADD) than ITEM_DB.txt.
Sometimes we need to learn new things in order to adapt a new stability instead of adapting the old methods.

 

1. TXT Version:
	12622,BOARDING_HALTER,Reins Of Mount,11,0,,0,,,,,0xFFFFFFFF,63,2,,,,,,{ setmounting(); },{},{ if( ismounting() ) { callfunc \"Func_Idiots\"; }

2. YML Version:
  - Id: 12622
    AegisName: BOARDING_HALTER
    Name: Reins Of Mount
    Type: Delayconsume
    Classes:
      All_Third: true
      Normal: true
      Upper: true
      Baby: true
      All_Upper: true
    Script: |
      setmounting();
    UnEquipScript: |
      if( ismounting() ) { callfunc \"Func_Idiots\"; }

Now which one is friendly and readable TXT over YML?

It's just like choosing eAthena (Bugg) over rAthena (Stability). (WAKE UP FOLKS) 
Then use the freaking TXT --> YML CONVERTER.

Edited August 30, 2022 by RikuTzy

[Vy Low]

agree! i prefer to use text db over yml. i still use 2020 revision before itemdb.txt to yml!

[Pride]

in some cases i would like YML  for example itemdb.yml is good and readable but for sure text db is one way for everyone to find it friendly to use. It would be better if we could still choose if we would want to continue with txt or yml. 

[Gidz Cross]

Yep. I agree to this one. The revision im building was before item yaml too.

[Velrond]

up for this