If ScenarioId mission header starts with 0, it will be parsed out in ServerData.json
Closed, ResolvedPublic
Actions

Description

Game Version number: Experimental 1.2.0.12

Modded?: Yes

Seize & Secure Scenarios
Seize & Secure Base
Capture & Hold

Issue Description:
When creating a mission header file, if the resource name begins with a "0" then it will be parsed out in the ServerData.json file where ScenarioIds are found. This has caused major issues with getting certain scenarios to start on a server, because it was assumed the ScenarioId in ServerData.json was the proper resource name.

Screenshots attached below

Details

Severity: Major
Resolution: Open
Reproducibility: Sometimes
Operating System: Windows 10 x64
Category: General

Steps To Reproduce

Create new mission config file.
Set class as SCR_MissionHeaderCampaign
Pray the system generates a resource number that doesn't start with 0.

Additional Information

First image shows the error when the server is starting up. The issue is not enough characters are in the resource number:

The second image shows the resource name/number given in the ServerData.json file:

This is the actual resource name in workbench (copied from Copy Resource Name(s)):
{01F1F6BDF405E3C0}

Event Timeline

Ironbeard created this task.May 21 2024, 12:22 AM

Ironbeard updated the task description. (Show Details)

Geez changed the task status from New to Awaiting internal Testing.May 21 2024, 11:21 AM

Geez closed this task as Resolved.Aug 1 2024, 11:05 AM

Geez claimed this task.

If ScenarioId mission header starts with 0, it will be parsed out in ServerData.jsonClosed, ResolvedPublicActions

Description

Details

Event Timeline

If ScenarioId mission header starts with 0, it will be parsed out in ServerData.json
Closed, ResolvedPublic
Actions