January 9th, 2016

borg_best_combo() was returning a crash from a report of the item description if the item was being pulled from the home.
The Amberites need to know that the level has changed when they use the Shadow Shifting ability.
If a borer monster was in a vault, and not able to flow to the borg, then the borg should not create a sea of runes and wait for the borer.
Sometimes we will see the borg fire several missiles or spells into a monter that has total cover from a wall. The game’s pathing routine is called project_path() but it also uses mmove2(). The borg used mmove2() for both needs. The two objects are not returning the same results so the borg believed that his path/aim would strike the target, but in project_path(), it would take a slightly different path and could catch a wall, thus stopping the path. I have switched the borg’s pathing to use the project_path() in the attack routines. So he should stop looping on this missed shots.
A crash related the use of Meteor Swarm was reported.
A randart with an activation might induce an inscribe loop if the item were “charging”
Some item inscriptions were not being recorded properly. This happened it the item had a super long name. So the borg will not inscribe an item if the item’s name is over 65 characters long.
Another slight rework of path guessing for bolts and beams. Fix in borg_lauch_bolt_aux().