Skip to content
New issue

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

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

Already on GitHub? # to your account

[Bug] Descent Class Selection variables disappear after calling new quest.ini #1376

Closed
DelphiDie opened this issue Oct 26, 2020 · 0 comments · Fixed by #1379
Closed

[Bug] Descent Class Selection variables disappear after calling new quest.ini #1376

DelphiDie opened this issue Oct 26, 2020 · 0 comments · Fixed by #1379
Assignees
Labels

Comments

@DelphiDie
Copy link

DelphiDie commented Oct 26, 2020

Describe the bug

While experimenting with a new scenario I noticed that there is a bug with the Descent class selection variables. These variables, which are created after starting a scenario, are not persistent and disappear after calling another quest.ini file. Thus, this information is lost in campaign games.

Scenario

JiT.zip

Steps to reproduce the behavior:

Example Scenario attached. Just start the game, select 2 heroes and 2 classes. Open log and press Alt-D to open debug menu. You will see 2 hero name variables and 2 class variables. Close log.

Then click on start to call another quest.ini. Open log again and you will notice, that the 2 class variables have disappeared.

Expected behavior

The variables should be persistent.

LogFile

No log file.

Screenshots

Screenshots attached,
Variables1
Variables2

Valkyrie Version

Windows Version 2.4.10

Desktop

OS Win 10 2004 x64

Smartphone

Not tested.

Additional context

No context.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants