[PATCH] Check the list of enabled mods when running a replay from the command line

[Itms]

Right now the replay mode fails when no mod is specified, we should check that and inform the user about what is happening.

Maybe this is part of a more general task, which is including mod data in commands.txt and other logging stuff.

We can use the list of mods in the commands.txt to make sure everything is fine.

[mimo]

It works for me on linux.

[Itms]

Apparently it's the VFS not finding the file, maybe related to mod selection changes?

I update the ticket description.

[Itms]

Um, I just understood that now the replay mode needs to know which mod(s) to load. I'm updating the docs and this ticket.

[elexis]

Trivial, just show the user a hint if g_args has "replay" but no "mod" argument. File: main.cpp

[Arno Hemelhof]

Displays an error message when you try to view a replay without specifying any mods

[Arno Hemelhof]

This patch just implements an error message. Should something else be done when nothing is specified, like loading public?

[elexis]

• Looks like it works, but in fact its broken as the XML library needs to be deinitialized on shutdown, see that CXeromyces::Terminate(); call below.
• should use LOGERROR (without newline at the end)
• "None were detected" doesn't add any information that isn't contained in the previous sentence.
• The message is clearly directed at users who are not familiar with the code or technical background. So the term "official mod" is a bit confusing / counterintuitive and should be avoided. I recall seeing "Did you mean this?" being printed out in some tool.

At least one mod should be specified! None were detected!\nIf you intended to use the official mod, do so by adding the argument '-mod=public'

• Maybe it would be better to first load the replay, extract the mods that specific replay wants, attempt to load them and then throw an error message if the specified mods were not found. Trying to replay something with a different set of mods doesn't seem to make any sense and if some developer wants to hack something with mods, he can just hack the replay file. This would be true for the visual replay as well.

[Arno Hemelhof]

Changed based on the remarks of comment 7

[Arno Hemelhof]

Thank's for the review. I based myself on the way it is handled when the replay file isn't found (Line 443) and CXeromyces::Terminate() isn't being called there. I have added the terminate call, used LOGERROR and rephrased my error message.

[Itms]

Hi, and thanks for your work so far. :)

When this ticket was created, we didn't have the list of enabled mods included in the commands.txt file. Now that we have that, it should be possible to check that the list of enabled mods is the same as in the commands file.

Currently the check is done in the visual replay menu but not when using the command line. I think a mismatch in the mod lists should trigger a warning instead of an error, so people using the command line are still allowed to do what they want.

This would be a more complex task. Would you be up for it? You can come to our IRC channel if you need more information.

Also, for next time, please take a look at our new way of SubmittingPatches: we're making changes to our review process.