Just to compare if he would make some things better than the player in the replay. Sometimes one may want to play a foreign replay from a specific point on as a normal game. Otherwise the possibility for saving a replay makes no sense at all In the past it was always possible to create a savegame from a replay and afterwards load it again. The "save-algorithm" must be adapted to save a replay to "replays" and otherwise to "saves". Is this then used as some kind of recovery if a multiplayer game crashed and the replay is somehow "misused" as an automatically saved game? I still do not get it completely to be honest. This must be confirmed from more people I think. I suggest to change the use of the Save button like this. Watching the first nine hours once, then hitting Save, and then being able to watch the remaining hour over and over again would be a nice feature. when debugging a bug in a ten-hours replay, I always have to resume watching from the start in every debugging session which is very annoying. … however, for debugging lengthy replays it would be very nice to change this behaviour instead to create a new replay by using the save button that is equal to the running replay starting at the point of the save. However, if I understood something wrong, please let me now and I'll be happy to fix This is what the bug is about as I understand it …Ĭurrently, I am not convinced that we have a bug here, rather a different behaviour many people seem to be used to. It used to be possible to continue a game saved from within a replay like a multiplayer savegame. Thus, my big question to you guys is: What is the purpose of saving a replayfile again? And why is it saved in "save"-folder but with gametype=kReplay? So, from my point of view, we have now an invalid file in "save" folder which is filtered out and not displayed (as described above). This results in a new savegame file located in "save" folder but with gametype=4 which is kReplay When watching a replay (Watch Replay and then select a file), the "player" (more specifically: the spectator) can once again save the replay. Now the tricky part as far as I understand: There are sometimes comments that it would be nice to be able to load SP games as MP and vice versa, but this would not work out of the box in all cases and is not a big problem, so changing this behaviour is not worth the effort imho. Is this behaviour generally accepted so far? It is quite a while this way already and nobody complained The first two look into "save" folder (but showing only single player save games, that is gametype=kGameSinglePlayer, or multiplayer savegames that is gametype=kGameMultiPlayer respectively) whereas the third one looks of course into "replays" folder. Multiplayer (Multiplayer -> LAN /Direct IP -> Host a new game -> Saved Game).SinglePlayer (Single Player -> Load Game).We have 3 different "entry points" for getting into a loading screen from the menu: In (which is the basis of all loading screens) we differentiate according to this enum and create different flavors of the savegameTable/savegameLoader which only shows the files of the "right" type.
wgf there is a preload-file which contains gametype= In the code, we have an enum class FileType which is used to differentiate the types and is saved along the file on disk (when you unpack a. So, the game creates automatically (in a specific interval?) files under "replays" while playing.
#Widelands saved replay manual
But there is no manual "save as replay" afaik. Whenever the player saves a current game, it is placed under "save" (both multiplayer and singleplayer games that are manually saved). We have 2 separate directories for save-files in. I need help understanding some fundamental requirements regarding replays and savegames.
0 kommentar(er)
