Trinitycore: [Bug]Missing Silithid Invaders

Created on 30 May 2014  路  6Comments  路  Source: TrinityCore/TrinityCore

Bug:
There's only 1 "Silithid Invader" spawned. There should be several.

Wowhead comments hint that they should share the same respawn pool with "Silithid Hive Drone", though there's nothing to support that claim.

Links:
Silithid Invader - http://wowhead.com/npc=4131
Silithid Hive Drone - http://www.wowhead.com/npc=4133

Core revision: 524152b5bf94
Database version: TDB 335.53
Addons: Anticheat1

Branch-3.3.5a Comp-Database Feedback-PatchFix Sub-Spawns

Most helpful comment

Technically all TC is "Legacy"

All 6 comments

/*
Autor: Rushor
Ticket: xxx
Descr.: Add some Bugs in 1k needels
*/

SET @FIRSTBUG   := xxx;
DELETE FROM `creature` WHERE `guid` BETWEEN @FIRSTBUG AND @FIRSTBUG+5 AND `id`=4131;
INSERT INTO `creature` (`guid`, `id`, `map`, `spawnMask`, `phaseMask`, `modelid`, `equipment_id`, `position_x`, `position_y`, `position_z`, `orientation`, `spawntimesecs`, `spawndist`, `currentwaypoint`, `curhealth`, `curmana`, `MovementType`, `npcflag`, `unit_flags`, `dynamicflags`) VALUES
(@FIRSTBUG, 4131, 1, 1, 1, 11143, 0, -6410.51, -3488.5, -71.1379, 3.93507, 300, 5, 0, 1280, 0, 1, 0, 0, 0),
(@FIRSTBUG+1, 4131, 1, 1, 1, 11143, 0, -6543.58, -3471.38, -80.4753, 0.418449, 300, 5, 0, 1280, 0, 1, 0, 0, 0),
(@FIRSTBUG+2, 4131, 1, 1, 1, 11143, 0, -6504.13, -3438.54, -70.034, 0.889688, 300, 3, 0, 1342, 0, 1, 0, 0, 0),
(@FIRSTBUG+3, 4131, 1, 1, 1, 11143, 0, -6479.96, -3285.22, -109.381, 5.2993, 300, 4, 0, 1280, 0, 1, 0, 0, 0),
(@FIRSTBUG+4, 4131, 1, 1, 1, 11143, 0, -6445.73, -3290.01, -105.235, 3.03068, 300, 5, 0, 1342, 0, 1, 0, 0, 0),
(@FIRSTBUG+5, 4131, 1, 1, 1, 11143, 0, -6375.22, -3460.83, -77.5705, 2.96746, 300, 4, 0, 1342, 0, 1, 0, 0, 0);

My spawnfix, not sure if that will be taken by people who want a 100% blizzlikeserver

@Crysicle : Yes, I have noticed exactly this in most of Jeutie's repacks the last year in my attempts to recreate the achievement "Loremaster of Kalimdor". I never thought about checking if it was blizzlike or not, I just went on killing the single Silithid Invader, went doing some other quests in the Shimmering Flats, came back for the respawn later. I guess I should have read the comments on Wowhead and tried wiping entire cave to see if it made any difference. Anyway, http://wowhead.com/npc=4131#comments is as close to a documentation as we can come by now, of what used to be.

Why was this closed when nothing was ever fixed, still valid on 3.3.5

SET @CGUID := XXXXX;
SET @POOL := XXXX;

DELETE FROM `creature` WHERE `guid` BETWEEN @CGUID+0 AND @CGUID+6 AND `id`=4131;
INSERT INTO `creature` (`guid`, `id`, `map`, `zoneId`, `areaId`, `spawnMask`, `phaseMask`, `modelid`, `equipment_id`, `position_x`, `position_y`, `position_z`, `orientation`, `spawntimesecs`, `spawndist`, `currentwaypoint`, `curhealth`, `curmana`, `MovementType`, `npcflag`, `unit_flags`, `dynamicflags`, `spawntimevariance`, `VerifiedBuild`) VALUES
(@CGUID+0, 4131, 1, 0, 0, 1, 1, 11143, 0, -6484.09, -3229.87, -112.36, 3.42467, 300, 3, 0, 1221, 0, 1, 0, 0, 0, 0, 0),
(@CGUID+1, 4131, 1, 0, 0, 1, 1, 11143, 0, -6472.31, -3243.75, -113.38, 5.96223, 300, 3, 0, 1221, 0, 1, 0, 0, 0, 0, 0),
(@CGUID+2, 4131, 1, 0, 0, 1, 1, 11143, 0, -6491.48, -3245.93, -112.497, 6.10384, 300, 3, 0, 1221, 0, 1, 0, 0, 0, 0, 0),
(@CGUID+3, 4131, 1, 0, 0, 1, 1, 11143, 0, -6462.86, -3297.58, -104.92, 1.41244, 300, 3, 0, 1221, 0, 1, 0, 0, 0, 0, 0),
(@CGUID+4, 4131, 1, 0, 0, 1, 1, 11143, 0, -6485.84, -3254.02, -113.549, 0.814107, 300, 3, 0, 1221, 0, 1, 0, 0, 0, 0, 0),
(@CGUID+5, 4131, 1, 0, 0, 1, 1, 11143, 0, -6488.36, -3323.74, -94.8076, 3.46016, 300, 5, 0, 1221, 0, 1, 0, 0, 0, 0, 0),
(@CGUID+6, 4131, 1, 0, 0, 1, 1, 11143, 0, -6496.03, -3325.49, -95.8035, 2.63545, 300, 3, 0, 1221, 0, 1, 0, 0, 0, 0, 0);

DELETE FROM `pool_creature` WHERE `guid` BETWEEN @CGUID+0 AND @CGUID+6 AND `pool_entry` BETWEEN @Pool AND @Pool+6;
DELETE FROM `pool_creature` WHERE `guid` IN(21317,21318,21314,21324,21323,21325,21327) AND `pool_entry` BETWEEN @Pool AND @Pool+6;
INSERT INTO `pool_creature` (`guid`, `pool_entry`, `chance`, `description`) VALUES
(@CGUID+0, @Pool, 0, 'Silithid Invader'),
(21317, @Pool, 0, 'Silithid Hive Drone'),
(@CGUID+1, @Pool+1, 0, 'Silithid Invader'),
(21318, @Pool+1, 0, 'Silithid Hive Drone'),
(@CGUID+2, @Pool+2, 0, 'Silithid Invader'),
(21314, @Pool+2, 0, 'Silithid Hive Drone'),
(@CGUID+3, @Pool+3, 0, 'Silithid Invader'),
(21324, @Pool+3, 0, 'Silithid Hive Drone'),
(@CGUID+4, @Pool+4, 0, 'Silithid Invader'),
(21323, @Pool+4, 0, 'Silithid Hive Drone'),
(@CGUID+5, @Pool+5, 0, 'Silithid Invader'),
(21325, @Pool+5, 0, 'Silithid Hive Drone'),
(@CGUID+6, @Pool+6, 0, 'Silithid Invader'),
(21327, @Pool+6, 0, 'Silithid Hive Drone');

DELETE FROM `pool_template` WHERE `entry` BETWEEN @POOL+0 AND @POOL+6;
INSERT INTO `pool_template` (`entry`, `max_limit`, `description`) VALUES
(@POOL+0, 1, 'Silithid Invader/drone pool 1'),
(@POOL+1, 1, 'Silithid Invader/drone pool 2'),
(@POOL+2, 1, 'Silithid Invader/drone pool 3'),
(@POOL+3, 1, 'Silithid Invader/drone pool 4'),
(@POOL+4, 1, 'Silithid Invader/drone pool 5'),
(@POOL+5, 1, 'Silithid Invader/drone pool 6'),
(@POOL+6, 1, 'Silithid Invader/drone pool 7');

However I also found that spawns in pools only gets set at server restart not on respawn so the same will always spawn until restart then will spawn differently.

Why was this closed when nothing was ever fixed, still valid on 3.3.5

all issues marked as [legacy] were closed some time ago

Technically all TC is "Legacy"

791899a6c751cd776ff6ace23d7d092ad1fcdf61

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ZenoX92 picture ZenoX92  路  3Comments

daddycaddy picture daddycaddy  路  3Comments

jerbookins picture jerbookins  路  3Comments

Tatara902 picture Tatara902  路  3Comments

Rushor picture Rushor  路  3Comments