![]() Overall, it feels like someone would need to completely redesign the borg from scratch if they really wanted to be sure that it works correctly on 3.4 or newer. For example, it may have died to that vibration hound due to spell menus not behaving as expected or being unable to activate an item or something. I was hoping to see the borg beat the game, but with all the bugs I've uncovered so far I doubt it will handle late game things correctly. I believe that attempt took around 2-3 hours with the delay between borg inputs set to just 1ms. My most successful borg character after all that has been a high-elf mage that made it to clvl 38 and died on dl 30 to a vibration hound. ![]() It would have inventory slots down to (s) and assume it should be able to hold 4 more things but the game would say it was full. So the borg would starve to death trying to pickup items. It seems to work now, but the first major bug I had with my version was that it would shrink the inventory by 4 slots. I copied the code that the game uses for making a new character and used that to rewrite the borg's respawn code. This one took me a while and I'm still not 100% sure I got it right. It would crash the game 100% of the time. I've been running the game inside a debugger so that lets me inspect the crashes and attempt a bandaid fix for those as well.Ĭharacter respawning was very broken. I've also had numerous crashes where the borg mishandled a pointer and made the game crash. I've found and fixed a bunch of those cases but problematic actions were enchanting, identifying, or branding anything in the quiver. The borg would also get stuck when trying to work with anything in the quiver. I have no idea if other spells are broken too. The priest kept trying to cast resist fire and frost and the game kept telling it illegal selection. I discovered that priest spells have moved around in the book. I've mostly had the borg making high-elf mages, but someone said I should try a priest. Not really the correct fix, but it was quick to implement. ![]() I "fixed" that by making it no longer wait for light sources to recharge. It must also have some sort of maximum wait logic because eventually it would stop waiting. So it would sit there waiting for an item to recharge that is never going to recharge. And the borg always wants to let items recharge before changing dungeon level. This was because they found a lantern of everburning and the borg mistook it for an item with activation. They would hang out in town for in game days before returning to the dungeon. I kept running into an issue where my characters would get to about level 20 and then they would dramatically slow down. The borg also gets confused about some items. In older versions of angband, it would always go to your inventory first and you would need to type / to see equipped. For example, if you have no unidentified items in your inventory but you do have one equipped then casting the spell will automatically go to your equipment. ![]() At some point the devs tried to make the menus more streamlined. This means that if it wants to cast the identify spell, it will send the mcf followed by the letter of the item. It parses the messages the game gives and it inserts its actions into the input stream. This matters because the borg tries to play the same way humans play. The second issue I encountered was that the game menus have changed a lot since the borg was originally designed. I eventually discovered that several versions of angband released with the borg included. The website that has traditionally hosted it seems to no longer be hosting. The first issue I encountered was that it was hard to find a copy of the borg. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |