Jump to content
Sign in to follow this  
lynx

BG1 cumulative vs Opcode 126: Stat: Movement Modifier

Recommended Posts

Posted (edited)

In case anyone still cares about bg1/totsc: while trying to figure out the speed discrepancy* between haste and the boots of speed (they don't double as in bg2), testing showed that incrementing works as setting. In other words, trying to increase the rate by 3 will actually slow you down (6 being the base bg1 rate). IESDP updated to match.

 

* somehow they make you effectively faster by setting your rate to 11 than haste doubling it to 6*2 = 12 !? The only explanation I currently have is that speed doesn't scale linearly with rate, but that would be quite silly.

Edited by lynx

Share this post


Link to post

Since I mentioned it, here's some more testing data for horizontal paths with the "set to" mode of the opcode. Testing with boots of speed setting movement rate, values are speed in px/s, plus delta:

  • 5: 75
  • 6: 90 (matching default), +15
  • 7: 105, +15
  • 8: 120, +15
  • 9: 120, +0
  • 10: 120, +0
  • 11: 235 (item default), +115
  • 12: crash
  • 13: crash
  • 14: crash

Utter madness. It's like 8 was the max at some point and then they bolted on 11 just for boots of speed.

The 15s could be 16s (one horizontal foot), but data is data.

Share this post


Link to post
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...