Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #1452  -  Cannot Cast Spells After Entering Forge
Posted Apr 27, 2020 - updated Apr 28, 2020   Shortlink: http://arx.vg/1452
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Not a bug" and resolution "NOT AN ISSUE".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    NOT AN ISSUE
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
Currently in the Forge area of the game (just defeated the Black Beast) and all spell casting randomly ceased to work. The game picks up my drawn rune shapes, but when casting the correct spell (or even clicking a precast spell from a scroll) makes the "spell failed" sound and nothing happens.
Steps to reproduce this issue
-Installed Arx Fatalis 1.21 -Installed Arx Libertatis 1.1.2 -Got all the way to the Forge with no issues -Magic suddenly stopped working forever

Haven't been able to try leaving the forge to see if magic starts working again. Will test tomorrow. I also have no save games that are not already inside the Forge and thus, bugged.

#1
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Apr 28, 06:57
This is by design, magic is not possible in the dwarven mines. There is a sign "Dwarf zone. No magic permitted." at the entrance but it's easy to miss.

Disabling magic is also used in a puzzle elsewhere in the game.

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to NOT AN ISSUE.