Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Write the original scenario filename to the spawnmap.ini [Basic] section. #419

Closed
CCHyper opened this issue Dec 21, 2022 · 0 comments
Closed

Write the original scenario filename to the spawnmap.ini [Basic] section. #419

CCHyper opened this issue Dec 21, 2022 · 0 comments
Assignees
@devo1929
Labels
feature

Comments

@CCHyper
Copy link

CCHyper commented Dec 21, 2022

The original scenario filename is lost when the client creates the spawnmap.ini file.

Various community based projects might need to know the original filename when implementing features, such as if the scenario follows a certain name format or if any pre-scenario load fixes to the scenario need to be applied.

Writing OriginalFilename=<filename.ext> under the [Basic] would be the simplest solution for this.
@CCHyper CCHyper changed the title Write the original scenario filename to the spawnmap.ini `[Basic] section. Write the original scenario filename to the spawnmap.ini [Basic] section. Dec 22, 2022
@devo1929 devo1929 moved this to 🚧 In Progress in XNA CnCNet Client Dec 22, 2022
@devo1929 devo1929 self-assigned this Dec 22, 2022
devo1929 added a commit to devo1929/xna-cncnet-client that referenced this issue Dec 23, 2022
@devo1929
CnCNet#419 Write the original scenario filename to the spawnmap.ini […
c7d4c90 
…Basic] section.
devo1929 added a commit to devo1929/xna-cncnet-client that referenced this issue Dec 23, 2022
@devo1929
CnCNet#419 Write the original scenario filename to the spawnmap.ini […
5bba1b0 
…Basic] section.
@devo1929 devo1929 moved this from 🚧 In Progress to 🏢 Dev Complete in XNA CnCNet Client Dec 23, 2022
@devo1929 devo1929 moved this from 🏢 Dev Complete to 👀 Under Review in XNA CnCNet Client Dec 23, 2022
devo1929 added a commit to devo1929/xna-cncnet-client that referenced this issue Dec 24, 2022
@devo1929
CnCNet#419 Write the original scenario filename to the spawnmap.ini […
7391261 
…Basic] section.
devo1929 added a commit to devo1929/xna-cncnet-client that referenced this issue Dec 24, 2022
@devo1929
CnCNet#419 Write the original scenario filename to the spawnmap.ini […
97c7456 
…Basic] section.
devo1929 added a commit that referenced this issue Dec 24, 2022
@devo1929
#419 Write the original scenario filename to the spawnmap.ini [Basic]…
acdcd84 
… section.
@devo1929 devo1929 moved this from 👀 Under Review to 🔍 In Testing in XNA CnCNet Client Dec 24, 2022
@CCHyper CCHyper added the feature label Jan 4, 2023
@Metadorius Metadorius moved this from 🔍 In Testing to 👍 Ready for Release in XNA CnCNet Client Jan 4, 2023
SadPencil pushed a commit to SadPencil/xna-cncnet-client that referenced this issue Oct 4, 2024
@devo1929 @SadPencil
CnCNet#419 Write the original scenario filename to the spawnmap.ini […
a5dbc3a 
…Basic] section.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@devo1929 devo1929

Labels
feature
Projects
XNA CnCNet Client
Status: 👍 Ready for Release
Milestone
No milestone
Development

No branches or pull requests
3 participants
@devo1929 @Metadorius @CCHyper