tome / Tales of MajEyal · Commits

Undeads

Alters a variety of Undead enemies and the Blighted Ruins enemies.
Should reduce the frequency of level < 5 characters being squished by a standard undead, by adding in a couple extra critters and bumping the levels up on the rest. This will make the Ruins of Kor'Pul and the Blighted Ruins a little easier.
The Bone Giant base has had its dex reduced by 30, but its movement speed increased by 50%. This is done to stop the Half Finished Bone Giant having 40ish dex which made it rather annoying if it rolls a shield rune. It doesn't get the movement speed bonus though.
Vampire and Wight minimum levels were also altered. They had a tendency to introduce themselves to the player on the same dungeon floor, rather than in a tiered progression. Wight talents were also tweaked so they aren't all the same.
All the Skeletons have been given descriptions by Hogulus.
Added an elite Skeleton Ninja for FUN.

Could do with some focus group testing and a few new tiles for the skeletons.

…er than the rest of the game (which is still very madly hard)

Small fixes

Typos be gone!

Fixing typos and grammar for 1.3.2

Occasional turn loss fix.

Game.tick now creates a copy of entitites' list to iterate over since iterating over a table while modifying it is undefined.

tickLevel now adjusts indices accordingly when entity is added or removed.

Reaver tweaks

Added Rot and Blight trees to Reaver, buffed Corrosive Worm/Poison Storm

Mindslayer corrections

Hi DarkGod :smiling_cat_face_with_heart_shaped_eyes:

Removes the rest of is_psionic_focus and makes Icy Kill non-metallic.

…els. Makes Wights a little more different to themselves. Adds a degenerated skeleton archer and skeleton magus which might need new icons. Should reduce the instances of nasty skeletons appearing too early.

…ent speed. The have long legs.

Archery woes (review?)

Since Shoot talent does not account for the run-out ammo in its pre_usee and just returns nil from action in that case (I believe that is intended for either player misuse or difficult scenarios), and as error message of not having one of two things equipped in exactly the right fashion have always been the same confusiong snippet through all archery talents, I've decided to unify the pre use check for all archery.
It comes in two fashions, counting wardens in and not counting wardens in; if desirable, those could be joined for added adventurer benefit, but I just left things as they are.
Playtesting suggests it indeed is working as intended now.
If there's anything to add to the picture while I'm at it, or if there are any problems, please comment.

Better error messages, check for nonzero ammo (so NPCs won't try to
shoot while being low on arrows).

Small fixes

Solipsist unlock didn't work on dream altar, should now

Fix Rune: Biting Gale not being used by tactical AI

Fix Rune: Biting Gale not being used by tactical AI

This was caused by the lack of a "radius" attribute in the talent definition.

While tactical.lua makes good use of the talent's "target" value, for the initial within_range check it ignores this and uses the sum of what it gets from getTalentRadius and getTalentRange. So, while Biting Gale had a perfectly good target table, because the radius was not stored in a separate radius value the AI was assuming it to have a range of 0, and thus never using it.

DG's verdict was to insist on better-written talents, rather than a more flexible check in the AI routine. Talent creators will need to watch out for this one.

Now, I've searched through all the talents, and not found any other cases exactly like this. I have, however, found a few which could be improved. I'll consider uploading a bundle of such fixes later.

This was caused by the lack of a "radius" attribute.

Which tactical.lua makes good use of the talent's "target" value, for
the initial range check it ignores this and uses the sum of
getTalentRadius and getTalentRange. So, while Biting Gale had a
perfectly good target table, because the radius was not stored in a
separate radius value the AI was assuming it to have a range of 0 and
thus never using it.

I've searched through the entire code base, and not found any other
cases exactly like this. I have, however, found a few which could be
mildly improved. I'll consider uploading a bundle of such fixes later.

Zone load tips

The game will now look in a zone's definition files for load_tips to display when loading a level of the zone, in that silly waiter titled Loading level...
Load_tips are an exact copy of the ones in module definitions except they can't contain images. They also shouldn't be too long because the waiter looks silly too stretched.

At least the players have something to look at in addition to just "Please wait while loading the level...". As mentioned on IRC, they could be used for special zones (Caldera, dreams, Angolwen). For other zones, they might not be added at all or just contain a copy of the normal loading-game tips.

The PR doesn't include any load tips for said zones because I can't into ToME lore :P

More fixes

Makes solipsist rares on nightmare+ less annoying

Caustic weapon fix

Fixes crash when corroding armor with the caustic weapon ego.

Small fixes

some forum complaints being fixed, nothing big.