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.

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

Redo scen details #632

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

NQNStudios
Copy link
Collaborator

@NQNStudios NQNStudios commented Feb 18, 2025

REWORKED: A feature flag denotes whether a scenario uses the new or old format for its metadata. With the old format (legacy scenarios and openBoE scenarios created prior to this PR) everything displays in the scenario picker as before, and scenario designers get 2 text fields to display however they want, and 2 text fields that are pretty much useless.

With the new format, Author and Contact info are formatted onto the first line in the scenario picker display. The scenario designer gets 1 line to write a teaser.

Fix #593

Also fix a bug where scenario ratings were appearing as integers ingame instead of the correct "G", "PG", etc.

@NQNStudios NQNStudios added enhancement scenedit Affects the scenario editor labels Feb 18, 2025
@CelticMinstrel
Copy link
Member

Some notes:

  • The inability to edit the scenario title later on is a regression from the original game, which stored title and credits as the first four scenario strings (title, who wrote x2, and contact info).
  • There was no author string in the original game. I added that at some point. I don't remember why, but if we're deprecating it I imagine we should check.
  • I couldn't find any place in the original source that used the contact_info value (there called scen_strs[3] if I'm not mistaken)… which makes me wonder how JV originally intended it to be used in the first place.

@NQNStudios
Copy link
Collaborator Author

NQNStudios commented Feb 18, 2025 via email

@CelticMinstrel
Copy link
Member

I guess I don't really get it. You're taking the author and contact info and stuffing them into "who wrote 1" in a specific format. If you want them in a specific format, why stuff them into a freeform field? I guess it does let the author decide to use a different format if they want, but what's the benefit of that?

I don't remember where the Who Wrote strings were displayed in legacy BoE (if at all), so it's hard to say if this change to their "identity" makes sense. Aren't they shown in the scenario select dialog?

@NQNStudios
Copy link
Collaborator Author

They're shown in the scenario selection dialog, yes. And the reason I prefer suggesting the format they should take, as opposed to actually forcing it, is that forcing it would require messing with the dialogxml for the scenario picker, and changing the scenario picker's code, too. I'd rather not take the risk of introducing new bugs doing that for little gain.

@NQNStudios
Copy link
Collaborator Author

Oh, and it keeps legacy scenarios displaying Who Wrote1 and Who Wrote 2 the way they intended.

@NQNStudios
Copy link
Collaborator Author

It is a little wonky. I'll rework it.

@NQNStudios NQNStudios added the bug label Feb 24, 2025
@NQNStudios NQNStudios force-pushed the redo-scen-details branch 2 times, most recently from 7ca6202 to a320f76 Compare February 24, 2025 19:57
@NQNStudios
Copy link
Collaborator Author

@CelticMinstrel reworked, with the PR description updated to explain the changes.

@NQNStudios
Copy link
Collaborator Author

I forgot to cherry-pick the menubar item commits

@NQNStudios
Copy link
Collaborator Author

There we go.

<text top='150' left='50' width='120' height='14'>Credits, Part 2:</text>
<text top='213' left='50' width='120' height='14'>Contact Information:</text>

<text name='title-text' top='65' left='50' width='120' height='14'>Title:</text>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the ID (name) for these various <text> elements should end in something other than -text – to me, that implies it should hold the actual title, not a label for the title. -label is the most obvious alternative. This applies to all the <text> elements that gained a new ID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug enhancement scenedit Affects the scenario editor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Redo & split up Scenario Details
2 participants