Adding an option to load a different savegame
Moderator: George Gilbert
Forum rules
Please read the Forum rules and policies before posting. You may
to help finance the hosting costs of this forum.
Please read the Forum rules and policies before posting. You may
to help finance the hosting costs of this forum.
-
Trantor
- Duke of Banville
- Posts: 2467
- Joined: Wed Mar 09, 2005 4:16 am
- Location: Berlin, Germany
- Contact:
Adding an option to load a different savegame
When you die, you can choose to "restart this game". But if you want to load a different savegame, you have to quit the game and restart it. An option to load any savegame would be very nice.
-
George Gilbert
- Dungeon Master
- Posts: 3022
- Joined: Mon Sep 25, 2000 11:04 am
- Location: London, England
- Contact:
Yes, this sort of thing has come up several times before. Basically, for performance / memory reasons, when you load a dungeon, RTC throws away all data that isn't needed in that game (all graphics / sounds / objects etc).
Whilst this means that game runs alot faster and uses alot less memory than it otherwise would, it also means that once a dungeon has been loaded once, loading other ones is much more tricky (as you'd have to reload everything, just in case it was required in the new dungeon).
As such, it's basically as fast to quit and restart than it would be for RTC to do it for you!
Whilst this means that game runs alot faster and uses alot less memory than it otherwise would, it also means that once a dungeon has been loaded once, loading other ones is much more tricky (as you'd have to reload everything, just in case it was required in the new dungeon).
As such, it's basically as fast to quit and restart than it would be for RTC to do it for you!
-
George Gilbert
- Dungeon Master
- Posts: 3022
- Joined: Mon Sep 25, 2000 11:04 am
- Location: London, England
- Contact:
Broadly speaking, yes.
For your amusement, this is also the root cause for the bug you found earlier today - the code that threw away the graphics was a bit too keen and threw away the graphics for the screamer slice when it should have spotted that (even though the screamer slice wasn't in the dungeon, it was dropped by a bonsai, and even though that wasn't in the dungeon it was required because it was created by the full cage) it was required.
For your amusement, this is also the root cause for the bug you found earlier today - the code that threw away the graphics was a bit too keen and threw away the graphics for the screamer slice when it should have spotted that (even though the screamer slice wasn't in the dungeon, it was dropped by a bonsai, and even though that wasn't in the dungeon it was required because it was created by the full cage) it was required.