Jump to content
  • 0

Npc Spawn Problem


Question

Posted

Hello!

I have few questions about Tyranossaurus spawn.

On L2jFrozen my T-rex spawn is in spawnlist. It seems I have the spawn coords in database-locations right acording to web info.

1.Is Tyranossaurus ar GBoss or raid boss? (as ride bosses have their own spawn table, grands again in regular, but their respawn is controlled in grand boss table) //-it says T-rex is Grand boss in my database type. Which means it should fallow that instance, but grand boss table, where resp of all Gbosses are, he is not listed there. Should he be?

2. Has anyone else come across T-rex not being/spawned in Jungle? And what was the issue, how did you resolve it?

 

p.s.

may b I'm missing simething out, should there be some q taken for it to spawn? I rememmber playing other chronicles above Interlude, and T-rex was there in the Jungle full time, after kill he had resp after some time.

3 answers to this question

Recommended Posts

  • 0
Posted (edited)

The point of Trex being on raidboss is only for the attribute "non lethal-able", which is shared amongst all raid bosses. If let's say you decide to add a "lethalable" attribute on NPC templates system, or on a shorter way you introduce a isLethabable and you "npcid = trex || instanceof L2RaidBoss", you could spawn it as a regular spawn. I don't see any point of it being a RaidBoss otherwise.

 

I'm not sure (don't rem), but Trex are supposed to get walking routes.

 

If he doesn't respawn after default spawn time, it probably uses default raid boss config.

Edited by Tryskell
  • 0
Posted (edited)

The thing is it hasn't spawned yet at all!

So should I realy move its spawn to raidboss_spawnlist table / and change his type from GBoss to Raidboss? I''m confused about changing his instance cause GrandBoss manager mentions him aswell.

 .java side/ GrandBossManager list it there: (but db grand boss table don't have it on) I'm confused..

* This class handles all Grand Bosses:
 * <ul>
 * <li>22215-22217 Tyrannosaurus</li>
 * <li>25333-25338 Anakazel</li>
 * <li>29001 Queen Ant</li>
 * <li>29006 Core</li>
 * <li>29014 Orfen</li>
 * <li>29019 Antharas</li>
 * <li>29020 Baium</li>
 * <li>29022 Zaken</li>
 * <li>29028 Valakas</li>
 * <li>29045 Frintezza</li>
 * <li>29046-29047 Scarlet van Halisha</li>
 * </ul>

I also find him by id talking here: WHY is it mentioned MonsterInstance now? ???

			case TARGET_TYRANNOSAURUS:
			{
				if (target instanceof L2PcInstance)
				{
					activeChar.sendPacket(new SystemMessage(SystemMessageId.TARGET_IS_INCORRECT));
					return null;
				}
				
				if (target instanceof L2MonsterInstance && (((L2MonsterInstance) target).getNpcId() == 22217 || ((L2MonsterInstance) target).getNpcId() == 22216 || ((L2MonsterInstance) target).getNpcId() == 22215))
					return new L2Character[]
					{
						target
					};
				return null;
			}
Edited by l2life

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]!      
    • ## [1.4.1] - 2026-01-29   ### ✨ New Features - **Short Description**: Server owners can add a short tagline (up to 240 characters) on the server info page, under the "Online" status. It appears in the server list (By Votes) for VIP, Gold VIP, and Pinned servers so players see a brief summary at a glance.   ### 🔄 Improvements - **Server Info Page**: Description field is limited to 3000 characters with a character counter; the textarea is vertically resizable. A second **Save Changes** button was added at the bottom (after the description) for easier saving. - **Server Name**: In My Servers → Edit, the server name is read-only and can no longer be changed (avoids accidental changes and naming conflicts). - **Server Rows (By Votes)**: Short descriptions wrap correctly and no longer affect row height; long text is clipped to two lines so the list stays tidy and consistent.   ---
  • 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..