Jump to content

Recommended Posts

Posted (edited)

Hello everyone, I wanted to share what I discovered. Many insurance had or have problems with the classic "NoItemName" error, the problem is the following:

 

1_ The order of the IDs that is even, example: 1, 2, 3, 4 ...... so on.

 

2_That the IDs do not exceed 99999, that may cause a bug.

 

3_Put an ID and its corresponding ID is not found in "armorgrp" or "weapongrp". If they added an item in "ItemName-e" and did not add the data accordingly in armorgrp or weapongrp, it will generate a bug, which will cause that from now on, everything they add will come out with NoItemName.

Example: I add 1 weapon with the ID 9300, and I don't add the data in weapongrp, obviously with that same ID. In that case the game will detect that this data is missing in weapongrp, which will generate a bug, and anything that is added after that ID 9300, will come out with NoItemName. (it happened to me)

 

4_A duplicate ID. Make sure that the IDs are different.

 

5_Remember to always save in your corresponding chronicle and 413. (If you save it wrong, the game will not recognize any name within the game).

 

 

Those are the errors that generate the classic NoItemName, take a good look and try again.

 

 

PS: Sorry, my English is not that good, I don't know English very well, so I had to use the good google translator. LOL

 

I hope it serves you. Greetings.

 

 

 

 

Hola a todos, quería compartir esto que descubrí. Muchos seguro tuvieron o tienen problemas con el clásico error "NoItemName", el problema es el siguiente:

 

1_ El orden de las ID que sea parejo, ejemplo: 1, 2, 3, 4...... así sucesivamente.

 

2_Que las ID no superen 99999, eso puede causar algún bug.

 

3_Poner una ID y no se encuentre su correspondiente ID en "armorgrp" o "weapongrp". Si agregaron un item en "ItemName-e" y no agregaron los datos como corresponde en armorgrp o weapongrp, generara un bug, lo cual hará que de hay en adelante, todo lo que agreguen salga con NoItemName.

Ejemplo:  Agrego 1 arma con la ID 9300, y no Agrego los datos en weapongrp, obviamente con esa misma ID. En ese caso el juego detectara que falta ese dato en weapongrp, lo que generara un bug, y cualquier cosa que agreguen luego de esa ID 9300, saldrán con NoItemName. (me sucedio)

 

4_Una ID duplicada. Mirar bien que las ID sean diferentes.

 

5_Recuerda guardar siempre en tu correspondiente crónica y 413. (Si lo guardas mal, el juego no reconocerá ningún nombre dentro de el juego).

 

Esos son los errores que generan el clasico NoItemName, miren bien y vuelvan a probar.

 

PD: Disculpen sin mi ingles no es tan bueno, no se muy bien ingles, asi que tuve que usar el buen google traductor. jaja

 

Espero les sirva. Saludos.

 

 

Edited by Kusaty
Posted
6 minutes ago, Kusaty said:

Hola a todos, quería compartir esto que descubrí. Muchos seguro tuvieron o tienen problemas con el clásico error "NoItemName", el problema es el siguiente:

 

1_ El orden de las ID que sea parejo, ejemplo: 1, 2, 3, 4...... así sucesivamente.

 

2_Que las ID no superen 99999, eso puede causar algún bug.

 

3_Poner una ID y no se encuentre su correspondiente ID en "armorgrp" o "weapongrp". Si agregaron un item en "ItemName-e" y no agregaron los datos como corresponde en armorgrp o weapongrp, generara un bug, lo cual hará que de hay en adelante, todo lo que agreguen salga con NoItemName.

Ejemplo:  Agrego 1 arma con la ID 9300, y no Agrego los datos en weapongrp, obviamente con esa misma ID. En ese caso el juego detectara que falta ese dato en weapongrp, lo que generara un bug, y cualquier cosa que agreguen luego de esa ID 9300, saldrán con NoItemName. (me sucedio)

 

4_Una ID duplicada. Mirar bien que las ID sean diferentes.

 

5_Recuerda guardar siempre en tu correspondiente crónica y 413. (Si lo guardas mal, el juego no reconocerá ningún nombre dentro de el juego).

 

Esos son los errores que generan el clasico NoItemName, miren bien y vuelvan a probar.

 

PD: Disculpen sin mi ingles no es tan bueno, no se muy bien ingles, asi que tuve que usar el buen google traductor. jaja

 

Espero les sirva. Saludos.

kai egw mporw na grafw stin diki mou glwssa kai na min katalaveis xristo.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • Tool that allows you to download the Lineage 2 game client directly from the official publisher CDNs. It fetches the CDN's file list and downloads every patch file, decompresses it (LZMA / Zip) and writes the finished client to disk — and can resume or repair an existing installation instead of starting over. It runs several client downloads at once through a batch queue, so you can prepare multiple regions or versions in a single session.   Supported: NCSoft CDNs (TW / KR / JP / NA) and  4game CDNs(RU / EU)   Download: https://drive.google.com/file/d/11SDcNASqO2GKOBT79LFu7mqvSRSJZvBS
    • https://l2avokado.com/ Hello everyone,   After some time of development, we've decided to open L2Avokado to the public in its current development stage. We're looking for players who enjoy Interlude and would like to help shape the project before its official release.   This isn't a "launch" announcement. Instead, we're inviting the community to log in, explore the server, test the systems we've built, and provide honest feedback. Whether it's bug reports, balance suggestions, progression ideas, or quality-of-life improvements, we'd love to hear them.   Our goal has always been to create an Interlude server that feels familiar while offering a fresh progression experience. We've intentionally avoided custom weapons, armor, and client modifications. Instead, we've focused on redesigning progression through reworked hunting grounds, quests, crafting, and gameplay systems while remaining compatible with a clean Interlude client.   At this stage, the core progression path has been implemented, including the main hunting grounds, quests, custom systems, and events. However, as the project is still under active development, there will inevitably be bugs, balance issues, and areas that require further polishing.   This is exactly why we'd like your help.   We're looking for players who are willing to: Test gameplay and progression. Report bugs and exploits. Suggest balance improvements. Share ideas for new features or quality-of-life changes. Help us build a server that the community genuinely enjoys playing.   The Client and System downloads are already available on our website, so you can jump straight into the game. We're also working on a dedicated launcher that will simplify installation and future updates.   If you're interested in helping develop a unique Interlude project and want your feedback to genuinely influence the direction of the server, we'd love to have you with us.   We look forward to seeing you in-game and hearing your thoughts on Discord. https://l2avokado.com/
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..