Problem with a new summoning skill

[Blitztech]

Hi all;

I started modding D2 (v1.12) about a week ago and have been making steady progress, but ran into a problem when trying to make an Ice Golem skill. Since it's replacing Fire Golem and has pretty much the same stats, except as cold, I copy/pasted Fire Golem where possible.

Skills.txt: copy/pasted, gave it a new name/skilldesc link, upped the index, changed 'summon' to 'IceGolem'
(also removed the 'nec' from 'charclass')
Skilldesc.txt: copy/pasted, linked to new skilldesc name, no other changes
MonStats.txt: copy/pasted, upped index, changed 'Id' to 'icegolem'

I've made no other changes than those listed above. When I summon the golem, it gives me a Clay Golem picture in the top left with the text 'Golem', the Gloam (from a3) sprite, and the summon doesn't follow me at all. It does, however, try to attack me when I summon it outside, but it does no damage.

As a point of curiosity, since the line right above it is 'willowisp8', I tried swapping the icegolem and willowisp8 lines. The summon then had the wraith sprite, with the same attempt-to-kill-me-outside behavior, and didn't follow. The line above icegolem now was wraith9.

I suspect that there's something causing it to reference the previous line for some inexplicable reason, but I haven't got enough experience with this to identify it and there doesn't seem to be anything significantly off about the preceding lines.

When deleting the icegolem line, nothing is summoned when the spell is cast (as expected).

Any assistance would be greatly appreciated!

PS - I tried following the New Summon guide (https://d2mods.info/index.php?ind=revie ... ew&iden=26) exactly, but got the same result. I reverted all my .txt files back before following the steps above.

[Necrolis]

this is the infamous blizzard chaining error, you need to use nafarius' fixed txt files if you want to avoid it

[kingpin]

this is the infamous blizzard chaining error, you need to use nafarius' fixed txt files if you want to avoid it

or correct them yourself

the d2xxxx.log file tells what chain errors you have if you using 1.10 atleast. know blizz changed log (saddly) in newer patches to less informative.

[Blitztech]

Well, on the plus side, it was a quick&easy fix. Thanks for that, swapped the files, did the c/p, and it was as easy as that.

For my personal knowledge, what causes this bug? Just a point of curiosity...

[BigMcLargeHuge]

OK, this thread has motivated me to go get the fixed .txt files as well I haven't had any problems with the ones I pulled out of the MPQ files, but why take chances?

[kingpin]

The game build a list of monster units to access quicker and reduse loadtime. The problem is with broken chain is basically that you point the next unit to be an ID that doesn't exist or add another unit use an baseID that exist and isn't linked together. What happend is then game try access the unit it cause a crash because the point can't be found in the broken link.

Then you have random crashes at startup / during gameplay. This is one of usual reason for cause it.

[Misty]

Hello. Got the bug caused by trying summoning ancient Talic, like all my new summoned ones work normally. When trying to create a Talic on the difficulty of nightmare or Hell, the game crashes, hes works only normal difficulty.
I tried changing the Ai and characteristics of the monster, it doesn't work.