Jump to content
  • 0

Pets: Null state & No name exists.


Question

Posted (edited)

The issue is experience on aCis 401 without any modifications on summon logic.

1. On every Summon item this is what I see.
https://prnt.sc/l8zjhfS_ZweB

2. Cannot interact with the summon (it doesn't open the summons's stats + skill/inventory)
3. On kill or on resurrection I receive this.

On die.
https://prnt.sc/dJEWa_hbW-SB
On resurrection.
https://prnt.sc/b1-rLyJJCZSy

Also the data from pets table in database.
https://prnt.sc/-vVn4BxlvuXT
Thank you in advance.

Edited by Vision

5 answers to this question

Recommended Posts

  • 0
Posted

this can be a datapack problem , probably you missing something check your summon_items.xml or i don't remember exactly name , try to copy datapack files again gameserver/data/xml.

  • Downvote 1
  • 0
Posted
17 minutes ago, LoVe+ said:

this can be a datapack problem , probably you missing something check your summon_items.xml or i don't remember exactly name , try to copy datapack files again gameserver/data/xml.

Already tried this nothing helped

Edited: Added screenshot from the database table of Pets ( name appears as null )

  • 0
Posted
Name appearing as null is fine, since it's the name the pet owner decides to put which is taken in consideration - and by default, no pet got any name.

The "null" appearance only occurs on custom (admin) messages, so it's not problematic aswell since nowhere else client finds such info. We can use template name if no personal name exists, but that's only for aesthetic purpose. I will make a commit for that.

The inventory flute with "no name exists" is also, perfectly fine from the moment the owner didn't set any name (same on L2OFF aswell). If he sets a name, the value is edited.

About the interaction itself, I tbh don't remember if I had to fix such issue between rev 401-latest. It works as intented on the PTS, which uses latest..
  • Upvote 1
  • 0
Posted

Client was fucked up, don't lock the topic yet would like to find the cause of this issue in order to post it here and help someone else with the same problem ! 🙂 

  • 0
Posted (edited)
5 hours ago, Odyssey said:

Client was fucked up, don't lock the topic yet would like to find the cause of this issue in order to post it here and help someone else with the same problem ! 🙂 

So, you need a name and not NoNameNpc or null returns everytime the pet hitting you...?

 

About "No name exists" on item, this will change when you first summon the pet. Then, it will show you "Name exists". If there's a name. Nothing to do with client files. Your files are ok, at least about the pets name.

 

I just add 3 lines at AbstractNpcInfo.java and SummonItems.java about the name. Go there, search for title, and you will get it.

But with this way, all pets(only item pets, not the pets of summoners or other class) it will show "Friendly Pet". To make the pets show names like "Wolf, Baby Wolf, Baby strider, Strider" you need to make it somehow like npcs getting name. More difficult, xml edit needed, can't explain it here..

But, another and easier way, it's to make pets getting name by their item's name(template). For example, the Wolf will get name Wolf Collar(you can change and this as well).

xzQsa7g.jpgcqy27fA.jpg

Edited by 'Baggos'
  • Like 1
  • Thanks 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

    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
  • 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..