![]() ![]() Probably a high chance of bricking your character as well though.Game is very frequently and seemingly randomly closes itself - as if alt+f4’d. I'm guessing that changes to the shared stash file however are made immediately and saved when closed (not hled in memory), and you have a short amount of time where crashing the game would result in the items being both on your character and in the stash. I'm guessing this is also the result of something funky going on with your character being held in memory. Of course, there's the other option that happens frequently in d2r - your game crashes and your save game is bricked. Changes to your character will usually be saved in the case of a crash. ![]() If you're willing to cheat in single player through a crash, then you should be willing to cheat by just cheating the normal way.Īnyways, On D2R, characters are held in memory throughout the duration of the game, making the force quit exit exploit not possible. You can also just do it this way on PC in D2R, so glitching wouldn't be as important. Of course, in legacy you can also just copy your characters files and try as many times as you want that way. So, if you want to cheese runewords in single player, you can save/exit, then enter game, then roll your runeword - if you get a bad result, you can force exit the game and try again. ![]() In legacy, you could enter your game, crash the game (or force quit) and changes to your character wouldn't be saved. Saved games are handled differently in d2r than they are in legacy. ![]() I bet you can replicate it by crashing your game through some other method on PC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |