it's an off course incomplete list of changes need to be done in engine.

This is for use in movement effects that bypass actually having to follow via normal walking so they don't home in on players that break LOS too quickly.

This let you ask for less accuracy on things like teleporting to the target when its out of LOS.

Adept prodigy now forces all known talents to update their passive effects (fixing notably Possessor's body storage count)

forceUseTalent's ignore_cd can be set to ignore_check_only to ignore cd *checks* but not ignore seting the talent to cooling down

Currently the AI makes guesses relative to your real location that increase in randomness every turn they don't see you.  This is very good for simulating intelligent chasing through hallways and such.

Where it breaks down horribly is when the target they're chasing moves a long distance quickly, especially over walls.  If you teleport over a wall the AI's guess cache is still at 1 turn, and if they can teleport too they will highly accurately.

This adds a last_special_movement property to Actors that represents the last turn they did a long distance or LOS cheating movement.  Currently only Actor.teleportRandom sets this.  Any NPC chasing a target that has this value set will have its guess cache set to the maximum randomness.

Any talent/function can set last_special_movement as appropriate.

A more ideal solution would be to have an algorithm with actual exploring/wandering behavior instead of a guess relative to your real location, but this should help.

Fix Actor.timedEffects having undefined behavior when effects are added during iteration and not preserving source

Somehow some talents (Osmosis Shield) can have their temporary values applied many times without being removed.  I can't reproduce it, but checking deactivating_sustain_talent on activation not just deactivation might fix it.

Fid ActorAI.aiSeeTargetPos not checking for invalid target location guesses the first turn it doesn't see the target directly

- Talent categories now parse their type ("Category / Subcategory") to put Category in its own field so you don't have to repeatedly parse the string.  This is useful for giving all Psionic/x talent categories a bonus, etc

- Add a new property ActorTalents.talents_mastery_bonus that lets you define a mastery bonus for all talents or all talents of one category

- Fix getTalentLevel not using getTalentMastery