M1 |
M2 |
055 |
001
Summary: | Save Game field always resets | ||
---|---|---|---|
Product: | Odamex | Reporter: | Catoptromancy <Catoptromancy> |
Component: | Client | Assignee: | Odamex Bug Reporter <odamex-bug-reporter> |
Status: | ASSIGNED --- | ||
Severity: | minor | CC: | mdvulture, mwoodj |
Priority: | P1 | ||
Version: | 0.7.x (Old) | ||
Hardware: | All | ||
OS: | All |
Description
Catoptromancy
2014-09-29 05:12:32 UTC
I implemented this behavior some years ago so that saved games could have a unique identifier on game consoles and handhelds when someone does not have a keyboard plugged in. I think this is still good default behavior but we could add an option to toggle it off. How about "date/time pwadname" as the auto field. Another idea is having a constant autofield at the start, but a user defined field after. Example: "date/time usercomment", then saving over it will bump the date/time but does not change usercomment. "usercomment" would be best as players, can label thier saves once and make it pwadname anyway. If the slot already has a name, it should not be overwritten with the timestamp. That sounds like the most egregious thing happening in this bug. r5162 fixes the worst part, now previously-named slots won't be overwritten with the date+time. Cato is this considered resolved by you? |