Minor fixes v14 (Baradin Hold)

Stiga

Gold Supporter
Veteran Member
66
2020
123
Location
France
Diverse issues with boss spawn ,loot etc. in Baradin Hold

Occu'thar 52363 / 54229 spawn had spawn 62363 which is an instant kill and no loot template.
Alizabal 55869 (other versions 57270 have no loot template or AIscript) had spawn 65869 which is an instant kill, no AIscript and no loot template.
Argaloth 47120 / 51350 not spawned > so found an unused creature spawn GUID in the range BH. Also added 25man difficulty entry (missing)

SQL:
UPDATE creature SET id = 52363 WHERE `guid`=172161; -- value was 62363 -- Occu'thar 52363 / 54229 spawn

UPDATE creature SET id = 55869 WHERE `guid`=172164; -- value was 65869 -- Alizabal 55869 (other versions 57270 have no loot template or AIscript)

-- 172154 free creature spawn / -- Argaloth 47120 / 51350
UPDATE creature_template SET difficulty_entry_1 = 51350 WHERE `entry`=47120;

INSERT INTO `creature` (`guid`, `id`, `map`, `zone`, `area`, `spawnMask`, `phaseMask`, `modelid`, `equipment_id`, `position_x`, `position_y`, `position_z`, `orientation`, `spawntimesecs`, `spawndist`, `currentwaypoint`, `curhealth`, `curmana`, `MovementType`, `npcflag`, `unit_flags`, `dynamicflags`, `walkmode`, `saiscriptflag`) VALUES (172154, 47120, 757, 5600, 5600, 2, 65535, 0, 0, 269.492, 1138.18, 160.921, 1.57189, 300, 0, 0, 19372500, 0, 0, 0, 0, 0, 0, 0);

Edit: For those who want GUID+1 for the creature spawn (best practice) (see conversation below)

SQL:
SELECT MAX(guid)+1 into @var FROM creature;

INSERT INTO `creature` (`guid`, `id`, `map`, `zone`, `area`, `spawnMask`, `phaseMask`, `modelid`, `equipment_id`, `position_x`, `position_y`, `position_z`, `orientation`, `spawntimesecs`, `spawndist`, `currentwaypoint`, `curhealth`, `curmana`, `MovementType`, `npcflag`, `unit_flags`, `dynamicflags`, `walkmode`, `saiscriptflag`) VALUES (@var, 47120, 757, 5600, 5600, 2, 65535, 0, 0, 269.492, 1138.18, 160.921, 1.57189, 300, 0, 0, 19372500, 0, 0, 0, 0, 0, 0, 0);


Edit: There may be some problems 10/25 man. I re-entered 25m and the bosses were 10m. If this can't work, I'll just use the 25m variants in both as these bosses are quite easy even with npc bots.

Edit. Retested and working well 10m and 25m. Boss ids remain the same at 10m, but loot is good in 25m. Not perfect but enough.
 
Last edited:

OMGhixD

Gold Supporter
Epic Member
522
2014
58
We might have some complications with that "insert into `creature`" query

If i recall correctly, such a query like this will pull the MAX value within the table creature and ensure we dont get a "duplicate" notice whatsoever, regardless of whoms world DB this is ran on.
Such a practice should ALWAYS be considered as it is the safest approach. It is very simple to make these kind of SQL checks and i recommend taking full use of it :)

SQL:
-- Instead of just adding the RAW/DEFINITE GUID from your DB, we use guid+1 instead. this will pull and use the MAX GUID VALUE but with ONE more value added to it.
INSERT INTO `creature` (`guid`, `id`, `map`, `zone`, `area`, `spawnMask`, `phaseMask`, `modelid`, `equipment_id`, `position_x`, `position_y`, `position_z`, `orientation`, `spawntimesecs`, `spawndist`, `currentwaypoint`, `curhealth`, `curmana`, `MovementType`, `npcflag`, `unit_flags`, `dynamicflags`, `walkmode`, `saiscriptflag`) VALUES
(guid+1, 47120, 757, 5600, 5600, 2, 65535, 0, 0, 269.492, 1138.18, 160.921, 1.57189, 300, 0, 0, 19372500, 0, 0, 0, 0, 0, 0, 0);

Regardless, well done!
 
Last edited:

Stiga

Gold Supporter
Veteran Member
66
2020
123
Location
France
We might have some complications with that "insert into `creature`" query

If i recall correctly, such a query like this will pull the MAX value within the table creature and ensure we dont get a "duplicate" notice whatsoever, regardless of whoms world DB this is ran on.
Such a practice should ALWAYS be considered as it is the safest approach. It is very simple to make these kind of SQL checks and i recommend taking full use of it :)

SQL:
-- SQL Check to pull the max value of column GUID and its records
$max = SELECT MAX( guid ) FROM creature;

-- We do not need a DELETE from in these queries, as the data we are attempting to insert
-- doesnt exist already. Thus we are ensured that it is clean data
INSERT INTO `creature` (`guid`, `id`, `map`, `zone`, `area`, `spawnMask`, `phaseMask`, `modelid`, `equipment_id`, `position_x`, `position_y`, `position_z`, `orientation`, `spawntimesecs`, `spawndist`, `currentwaypoint`, `curhealth`, `curmana`, `MovementType`, `npcflag`, `unit_flags`, `dynamicflags`, `walkmode`, `saiscriptflag`) VALUES
($max+1, 47120, 757, 5600, 5600, 2, 65535, 0, 0, 269.492, 1138.18, 160.921, 1.57189, 300, 0, 0, 19372500, 0, 0, 0, 0, 0, 0, 0);

Regardless, well done!

I totally agree with your point above, but I wanted a GUID in the same group range for the others in that instance and that one was not used.
Even though I know it's not necessary, I just like to keep things grouped. Personal choice.
 

OMGhixD

Gold Supporter
Epic Member
522
2014
58
I totally agree with your point above, but I wanted a GUID in the same group range for the others in that instance and that one was not used.
Even though I know it's not necessary, I just like to keep things grouped. Personal choice.

Just to point it out, my query was a tad incorrect (see my reply again for the corrected version)

I get that you want to group it and all. But this is genuinly bad practice. Luckily 172154 does not exist in the creature table from before, so from what i can see it wont really cause any issues (atleast not as of right now). But by simply doing "guid+1" we dont really have to have second thoughts if it will cause issues in the future or whatever. Your DB might be outoff sync or ahead of other DBs, but "guid+1" will take every DB and their uniqueties into account and ensure none of them run into issues.

Regardless, grouping in the creature table is rather uneccessary. It is already a clusterfu*k and will most likely continue to remain that way. I'm pretty sure even blizzards creature table is a clusterfu*k :p

And yes, Blizzard also has a form of "creature table". Not exactly the way we have it, but more or less the same just in a different format, method or whatever.
 

Stiga

Gold Supporter
Veteran Member
66
2020
123
Location
France
Just to point it out, my query was a tad incorrect (see my reply again for the corrected version)

I get that you want to group it and all. But this is genuinly bad practice. Luckily 172154 does not exist in the creature table from before, so from what i can see it wont really cause any issues (atleast not as of right now). But by simply doing "guid+1" we dont really have to have second thoughts if it will cause issues in the future or whatever. Your DB might be outoff sync or ahead of other DBs, but "guid+1" will take every DB and their uniqueties into account and ensure none of them run into issues.

Regardless, grouping in the creature table is rather uneccessary. It is already a clusterfu*k and will most likely continue to remain that way. I'm pretty sure even blizzards creature table is a clusterfu*k :p

Luckily no. I checked beforehand ofc. Nevertheless, I totally agree with your points.
I normally use the best practice that you stated above for the same reasons you stated.
 

OMGhixD

Gold Supporter
Epic Member
522
2014
58
Luckily no. I checked beforehand ofc. Nevertheless, I totally agree with your points.
I normally use the best practice that you stated above for the same reasons you stated.

Good to know :)
 

Jenniy

I collect profile flairs.
Silver Supporter
Senior User
351
2020
70
Yay! More spawns fixed due to your mighty vigilance; Many thanks to you Stiga!
 
Top