Opened 9 years ago

Closed 8 years ago

Last modified 8 years ago

#1091 closed change (invalid)

Allow import of monster memory even if we can't import old characters

Reported by: takkaria Owned by:
Milestone: Triage Keywords: loadsave
Cc:

Description

This will mean I'll feel less bad about breaking savefile compat...

Change History (6)

comment:1 Changed 9 years ago by magnate

See also #950

comment:2 Changed 8 years ago by magnate

  • Milestone changed from 3.2.0 to 4.0

Not a bug or refactor: punting to 4.0

comment:3 Changed 8 years ago by magnate

  • Status changed from new to confirmed

comment:4 Changed 8 years ago by magnate

  • Type changed from bug to change

comment:5 Changed 8 years ago by magnate

  • Keywords loadsave added; blocker removed
  • Milestone changed from 4.0 to Triage
  • Resolution set to invalid
  • Status changed from confirmed to closed

I don't think this is a valid ticket any more. We have a block-based savefile system which means we will always be able to import characters from 3.2.0 or later - this is independent of #950, which will take monster memory out of the savefile. Before #950, importing monster memory is automatic with loading the savefile, afterwards it will be automatic with the new mechanism. There is no possibility of importing monster memory from pre-3.2.0 savefiles anyway, so there is nothing for this ticket to do.

comment:6 Changed 8 years ago by takkaria

I don't think we'll always be able to import savefiles - object lists, monster lists might change too much, artifacts might get deleted, the internal structures of the game might change too much. But you're right that #950 will make it all moot.

Note: See TracTickets for help on using tickets.