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.

  • Haha 1

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

    • TG Support: https://t.me/buyingproxysup | Channel: https://t.me/buyingproxycom Discord support: #buyingproxy | Server: Join the BuyingProxy Discord Server!  Create your free account here
    • Dalam World — This is a new gaming project that brings together all the mechanics of your favorite games! I want to say right away that the game will run on all devices: Windows, Linux, macOS (Intel/Apple)! The Dalam World client features advanced graphics that will look great! The client also provides stable FPS even with a huge number of players! Dalam World is not a Salve or Chronicle client ported upward — it’s a completely remade game on its own proprietary game engine! Dalam World servers allow more than 100,000 people to exist in a single world without virtual instances, thanks to server technologies built with Elixir and Rust! Dalam World is the childhood game we love so much! From each of our favorite MMOs we took only the best elements! Low system requirements will let the game run on an old laptop! We redesigned the game so there are no bots or real-money traders! Game website: https://Dalam.World Game forum: https://Dalam.World/forums/ For arbitragers: https://careers.dalam.world/ Discord: https://discord.gg/vbQ347nuxd Telegram: https://t.me/+u1DNZPzscaRmNjYx Opening July 16, 2026 at 16:00 UTC!  
    • I'll give you my wallet if you want, haha
    • To make up for some of the waiting time we’re hosting a 3v3 Tournament on open Beta, and this time we’re raising the stakes with a $1,300 prize pool 💰   🏆 PRIZE POOL BREAKDOWN (Over 2000$ Worth of prices total)   🥇 1st Place — $700 🥈 2nd Place —$300 🥉 3rd Place — $200 🏅 4th Place — $100  5th -6th Place - $100 in Gold Coins each    All Participating Teams: $50 in Gold!   All Prices will be Paid out instantly after the tour, no waiting time and conditions. This is not simply a marketing move, we want to give back to the community.   📅 Date: Wednesday 06.05.2026 ⏰ Time: 20:00 Central European Timezone (Berlin) 📍Format: 3v3   ⚔️Why join? Cash Prices for top 4 and rewards for all participants Payments to winners sent out straight after the tournament - No waiting time or rules that you have to play live server to obtain the reward. Clean format, smooth matches, and solid prize pool and a chance to experience our brand new files   📝How to join: Form your 3-player team Group Leader Sign up here: ⁠📍・3v3-tour-registration (Include Name of Group, Name of Group Leader)   Be ready on match day!     A separate post with rules for the tournament and class setups will follow shortly.   Tag your teammates, lock in your roster, and get ready to compete. We'll be happy to see you on the OBT!   💬 Questions? Ask in ⁠🎫・ticket or send us a message   See you on L2Dark! 😏   Discord: https://discord.gg/FAJwnFpb8M
    • You should check if that condition is supported by your current sources. You can find this in  DocumentBase#parsePlayerCondition If it isnt there and you want to follow the same pattern of the other item conditions, create a custom condition to parse the classId (or multiple class ids) (there are examples to copy the code). Alternatively, you can create your own condition handler. Your condition should look like this: <cond msgId="1518"> <or> <player classId="ADVENTURER" /> <player classId="PALADIN" /> </or> </cond> or <cond msgId="1518"> <or> <player classId="93" /> <player classId="5" /> </or> </cond>  
  • 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..