drtchops

Cheat Quicksaves

Aug 9th, 2016
718
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.69 KB | None | 0 0
  1. Hi I figured out why cheat quicksaves happen. In DishonoredInput.ini, there's the lines:
  2. BaseBindings=(Name="GBA_QuickSave",Command="Dis_Save 15")
  3. BaseBindings=(Name="GBA_QuickLoad",Command="Dis_Load 15")
  4.  
  5. This is the definition for the QS and QL commands that get bound to whatever keys you want. In 1.4, the value is 15, which is the "quicksave" value. Lower values just seem to break it, and higher values make it save to different slots (16 is Dishonored0.sav, 17 is Dishonored1.sav, etc).
  6.  
  7. In 1.2, the "quicksave" value was actually 13, not 15. I have no idea why Arkane changed the value in the patch but they did. Normally when you downpatch and launch the game, DishonoredInput.ini gets updated and the commands get set to 13. This makes them act like normal quicksaves and the delay still exists.
  8.  
  9. However, if you downpatch, do the normal ini edits, and set the file to read only before launching the game, the ini gets stuck with the 1.4 value of 15 instead of 13. Since the values are shifted down, that means the quicksave command is actually saving to slot 2 (Dishonored1.sav). This is actually a hard save instead of a quicksave, which doesn't have a delay on it at all. With this config you can QL immediately after QSing, aka the cheat quicksave. This is also why the save isn't marked as "Quicksave -" in the load menu like usual.
  10.  
  11. So, do we allow this change? As of right now we don't allow changes to any of the BaseBindings or Commands in that ini. However, we already have lots of runs on the leaderboard that accidentally had this edit done.
  12.  
  13. If we allow it, do we allow any other command editing in that ini?
  14.  
  15. If we ban it, do we reject all runs that have it, or just ban it going forwards?
Add Comment
Please, Sign In to add comment