Help needed with ruleset conversion from 7.15 to 8.0 exe

[Varlad]

Hello,

I’m a new user on the forum, and I’m working on converting some rulesets from the old 7.15 exe to 8.0 exe, and I keep encountering some errors that I can’t resolve. Since there are many files involved, I was wondering if there is a way to automate the conversion or if there’s a better way to identify the errors, as I’m having trouble interpreting the OpenXcom log.

Thank you in advance for any help, and apologies for my English. If this question doesn’t belong in this forum, please feel free to move it to the appropriate section.

So far, all the rulesets in my mod work perfectly with 7.15.

Thanks again and best regards.

[Meridian]

If you're not a bot, feel free to ask about specific errors here.

[Varlad]

Hello again:
No, I am not a bot. I apologize if my question may seem pretentious, but I'm bringing this up because.... I have many files that may fail with the current 8.0. Here I put a log with one of the many errors that, I think, will appear to me from now on. I can't make any progress and I don't understand the logic of the new exe. Until now I have worked with 7.15. Here is the first error that appears in the log:

C:/Users/Administrator/Desktop/Open XCOM BMF/Open XCOM BMF/standard/xcom1/soldiers.rul: Rapidyaml ERROR: reached end of file while looking for closing quote.

If the ruleset is needed I can also provide it. That's why I was asking for some application or method to automate as much as possible, if such a thing exists and is possible, the conversion work. It is not for lack of desire to work, on the contrary, but it is that I can not find a logical method of work, or I do not understand how is the current one, although it has been properly explained in the forum, to make the conversion.
Again, thanks in advance.

[Meridian]

Your question is not pretentious.

It's your email address that is suspicious.
It looks like most of the classic spambot emails.
I even found it banned several times on forum protection sites.

Anyway, the issue you're seeing is most likely caused by incorrectly formatted string in soldier name files.
Probably even the classic 'Akamu name
For more details, have a look at this: https://openxcom.org/forum/index.php?topic=12367.msg168433#msg168433

You can solve it either by removing the single quote from the name, e.g. change  'Akamu to Akamu
or by adding double quotes around it, e.g. change 'Akamu to "'Akamu"

Example of a fix in another mod: https://github.com/SolariusScorch/XComFiles/commit/b31a1d3aee2a8ea521d604592d7342753e18e823

[Meridian]

Btw. if you won't be able to fix it yourself, feel free to upload the whole mod here and I will fix it for you for free.

[Delian]

That's in the standard folder tho. When you upgrade the exe file, standard and common folders should be upgraded as well.

Also, lol, it does look like the first post was written and posted by a bot. That LLM-like perfect english is unmistakable. And then that last paragraph in the 3rd post with totally broken english is the guy writing himself. Using some sort of "AI assistant"?

[Meridian]

That's in the standard folder tho. When you upgrade the exe file, standard and common folders should be upgraded as well.

The `soldiers.rul` is in the standard folder, yes.
But the error is not in that file, but in one of the many soldier name files it references (which is not visible in the error message)... which can be coming from a mod.

Also, lol, it does look like the first post was written and posted by a bot. That LLM-like perfect english is unmistakable. And then that last paragraph in the 3rd post with totally broken english is the guy writing himself. Using some sort of "AI assistant"?

Nothing wrong about using AI assistant.

Just don't use emails like j.en.n.ife.rl.o.pe.z@gmail.com when registering, because that's how all spam emails look like.
The guy was seriously lucky I didn't delete his account automatically (as I delete literally hundreds such accounts daily).