Small feature patch for Angband SVN

[PaulBlay]

I've made a 'new feature' that could be added to Angband (or a variant). Changes made to the following files from the SVN version:

\src\init1.c
\src\defines.h
\src\monster\monster2.c
\src\monster\types.h
\lib\edit\monster.txt

(Hopefully that's all of them)

If the patch files (attached) are applied to Angband a surprise awaits the player in the town level (obviously no surprise if you look at the contents before applying them ;-)

I was going to put this on the development newsletter, but I thought I'd 'christen' the new Development forum.

[EDIT] Hey! It's my 100th post. (just noticed)

[pav]

Ahaha, funny. You can put all the chunks into a single patch file, BTW, not a file per file. Nice idea how to axe the FORCE_MAXHP flag, that could be applied in Vanilla on it's own.

[PaulBlay]

Ahaha, funny. You can put all the chunks into a single patch file, BTW, not a file per file. Nice idea how to axe the FORCE_MAXHP flag, that could be applied in Vanilla on it's own.

'Associate' could have gone into the third, unused, W: slot but that looked a little risky with the 'power' business. I would also suggest that monsters with FRIEND, FRIENDS, ESCORT, ESCORTS that have non-zero 'associate' values could use that specific monster instead of the usual routine.

I (mis)used rarity=0 to mean "never place this monster in normal dungeon generation." It seems to work (but I don't know why )

[Pete Mack]

I (mis)used rarity=0 to mean "never place this monster in normal dungeon generation." It seems to work (but I don't know why )

Because that's what rarity 0 means. I hope you didn't replace QUESTOR with this, because QUESTOR monsters are eventually regenerated after *Destruction*.

[zaimoni]

I've made a 'new feature' that could be added to Angband (or a variant). Changes made to the following files from the SVN version:

\src\init1.c
\src\defines.h
\src\monster\monster2.c
\src\monster\types.h
\lib\edit\monster.txt

(Hopefully that's all of them)

If the patch files (attached) are applied to Angband a surprise awaits the player in the town level (obviously no surprise if you look at the contents before applying them ;-)

I was going to put this on the development newsletter, but I thought I'd 'christen' the new Development forum.

[EDIT] Hey! It's my 100th post. (just noticed)

An interesting strategy to de-hack Z's Warriors of the Dawn (just configure the probability as well).

[CunningGabe]

I would also suggest that monsters with FRIEND, FRIENDS, ESCORT, ESCORTS that have non-zero 'associate' values could use that specific monster instead of the usual routine.

I think this is a really cool idea. I once thought it would be amusing to have two uniques -- Tweedle-Dum and Tweedle-Dee -- who always appeared together. You could have vampires appearing with a vampire bat escort. There are lots of fun possibilities.

[Big Al]

I think this is a really cool idea. I once thought it would be amusing to have two uniques -- Tweedle-Dum and Tweedle-Dee -- who always appeared together. You could have vampires appearing with a vampire bat escort. There are lots of fun possibilities.

Amusing thought:

N:618:Tweedle-Dum
W:0:1:0:0:619
F:UNIQUE | TRANSFORM

N:619:Tweedle-Dee
W:0:1:0:0:618
F:UNIQUE | TRANSFORM

It would never die!

[Magnate]

Ahaha, funny. You can put all the chunks into a single patch file, BTW, not a file per file. Nice idea how to axe the FORCE_MAXHP flag, that could be applied in Vanilla on it's own.

Um ... hasn't FORCE_MAXHP already gone? Monsters now have specific hp figures, not XdY.

CC

[PaulBlay]

Um ... hasn't FORCE_MAXHP already gone? Monsters now have specific hp figures, not XdY.

Yes, that was nothing to do with me. The flag was still hanging around in the flag list in one file, but that was all.