Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #963  -  The first earthquake does not trigger in the mine after goblin prison
Posted Jan 18, 2017 - updated Jul 03, 2021   Shortlink: http://arx.vg/963
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Fixed" and resolution "POSTPONED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Fixed
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    bsxf47
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    POSTPONED
  • Priority
    Regression
  • Reproducability
    Always
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png 1.2
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
The first quake should trigger shortly after tearing the first encountered spider web in the abandoned mine (level15), right after torch ignition tutorial.

This works in 1.1.2 but not in available snapshots or current code.

Tearing the web creates a timer "qk" which should initiate the earthquake effect after 2 seconds (spider_web_0013/spider_web.asl:6 or 10). However, the original object to which the timer is tied (spider_web_0013) gets replaced by spider_web_broken and the former is destroyed, which also clears the quake timer.
Steps to reproduce this issue
  1. Breach the spider web
  2. Observe the nonexistent earthquake

#1
icon_reply.pngReply
Comment posted by
bsxf47
Jan 18, 16:44
A file was uploaded. Save just before the spider webicon_open_new.png
#4
icon_reply.pngReply
Comment posted by
Guest user
Jun 03, 01:46
I have the same issue. The earthquake does not trigger.
#6
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jul 03, 00:06
This has been fixed in the latest development snapshot by adding a special case for this entity to the engine. In the future that fix should be changed to be a script patch instead.

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Fixed.
  • The resolution has been updated, from Not determined to POSTPONED.
  • This issue's progression has been updated to 100 percent completed.