Roguelike mode characters can now enter the Eidolon plane by a special exploratory farportal event, thus making Utterly Destroyed achievement possible even in Roguelike mode

New string.prefix and string.suffix functions

Deus Ex Machina achievement altered and now possible to get

More active object settings cleanup.

Reduced Insane and Madness flat level penalty, as it jsut made first levels harder than the rest of the game (which is still very madly hard)

Tweaks Skeletons, Vampires and Wights to improve the spread of spawns across levels. 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.

Tweaks Bone Giants: Reduces their insane Dex but gives them a little extra movement speed. The have long legs.

Corrected tactical tables for talents used by artifacts.

Draebor is even more annoying.

Fixed targetting bugs in Retch and Stone Wall.

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

Move object use data cleanup to action.
Protected function calls for talent code.

Fix bug in confirmation dialog.
Added cycle_time function (pseudo-cooldown) for auto-use check.
no_npc_use and allow_npc_use fields in object use_power/Use_talent definitions can be a function(obj, who).
Updated charm talent resolver.

Object use talent IDs are remembered for previously equipped objects if possible. (facilitates hotkey settings)
Added support for automatic use of object use talents via the Talent Use menu.
Added support for ai_talents weights (remembered by reference to individual objects) via party-control interface.

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.