Known issues (0.35 & 0.35b)

[shadowofze]

Authored by Claude (Anthropic's AI assistant), posted on behalf of the project owner, shadowofze. This post is locked and kept up to date as issues are found and fixed. Have more details on one of these? Post them in Bug reports.

REPORT ISSUES TO ME VIA THE ISSUES FEATURE ON GITHUB SO I CAN KNOW WHAT IS BROKEN THANK YOU

Known problems in the current release (0.35 / 0.35b), so you don't need to report them again. Only open problems are listed here. Fixes made after this release are listed in CHANGELOG.md as they are made.

Known bugs

• Summoner's Hall and Darkness Falls raid events for bots, open to all three realms, with PvP inside and on the way. Bots have now cleared Summoner's Hall on their own; Darkness Falls bosses are not all cleared yet.

• RvR sieges rarely reach an outcome. Bots don't yet take keeps or relics from another realm on their own. They now set up and fire rams, catapults, trebuchets and ballistas, gather into full groups and attack as soon as they arrive, but no keep or relic has fallen to a bot siege in testing yet. Sieges are being reworked to play out like real players: a realm quietly gathers and strikes, the defenders rally once the attack lands, and a third realm sometimes joins in.

• Epic dungeon raids never finish. Bots haven't yet cleared Caer Sidi, Tuscaran Glacier or Galladoria through to the final boss on their own. One cause has been found: most of these bosses (and Summoner's Hall's) can't be hurt once they are dragged away from their lair, and bots kept fighting them there instead of leading them back the way players do. A fix is being tested.

• The game client can crash during /raid 80 play. The client has closed on its own in a /raid 80 keep assault and while spawning /raid companions. It reads a character or object model that was already deleted (both crashes were at the same spot, game.dll offset 0x25A507), most likely when many models are created, removed or changed around you at once (raid companions, temporary siege engines). Being looked into.

• Quest dialogue doesn't pop up on some middle steps. On some classic quests, talking to the NPC for a middle step moves the quest on to the next step, but no quest dialogue window appears. Seen in Enchanting Willow (Hibernia) when talking to Ciar and to Lucan.

• The Sluaghbinder has no realm abilities. No realm abilities are offered to the Sluaghbinder (0.35b).

• The launcher has no options for raid and siege sizes or automatic events. Planned options in the launcher's Options, changeable only while the server is off, starting at today's values: how many attackers, defenders and third-realm interferers join relic sieges and RvR keep sieges, and the chance (%) of third-realm interference; how many bots PvE events use, both the starting amount and the total assigned; switches to turn off automatic RvR/relic sieges and automatic PvE events (epic dungeons, dragon raids, Summoner's Hall and Darkness Falls); and separate switches for no automatic rallies in PvE and in PvP. Along with these options, the realm chat rally calls will stop giving exact numbers (they always say "at least 200" or "300" players for PvE events, and the same for RvR); every rally message that names a count will use vaguer wording, game-wide.

• Quests likely give too little experience. Quest experience rewards seem lower than what 1.65 sources show. Reported; not looked into yet.

On Hold (Difficult, Minor, Risky, or Impossible fixes)

• Dead bots stand back up with 0 health. After a gamebot or companion bot dies, a copy of it can appear standing near its corpse with 0 health and stay targetable for a while before it disappears. Bots should only leave a corpse, the way players do. Possibly an NPC packet issue: bots are sent to the game client as NPCs, which have no riding, sitting or dead state the way players do.

• Groups rest where a fight ended instead of gathering around their leader first.

• Bots on stable routes aren't shown riding a horse the way players are (visual only). Possibly an NPC packet issue: bots are sent to the game client as NPCs, which have no riding, sitting or dead state the way players do.

• Bots don't show the sitting animation while resting the way players do with /sit (visual only). Possibly an NPC packet issue: bots are sent to the game client as NPCs, which have no riding, sitting or dead state the way players do.

• Bots don't take part in housing at all.

• Bots don't do any crafting. Crafting isn't needed on this server: it uses random gear (ROG) drops, as the Phoenix and Atlas freeshards did.

• Bots move slowly for a while after being resurrected. A bot comes back from a resurrection or a release below a third of its health, where the low-health slowdown applies (a real game mechanic, kept for PvP), and it can keep walking at that slower speed even after it has healed, until it heads somewhere new.

Found something that isn't listed here? Post it in Bug reports.