[Minor] Fix AltNextScenario= not taking effect

[Fly-Star-him]

An extension to “AltNextScenario=” has been made so that it can now be started with any variable with the name “<Alternate Next Scenario>”, but of course the original hardcoding still works.

[Fly-Star-him]

Hey, why is this showing up with a display error.

and how it should generate a nightly.

[chaserli]

I don't know if you are referring to issue #1108 and #1140, if yes then check if dde700f fixed it already

[Fly-Star-him]

I don't know if you are referring to issue #1108 and #1140, if yes then check if dde700f fixed it already

确实有用，那我只留下AltNextScenario=这部分修复就行了。

Machine translation: It does work, so I'll just leave the AltNextScenario= part of the fix.

[Fly-Star-him]

if the variables are not supposed to be editted in the function, we'd better avoid using reference here. Namely LocalVariables, GlobalVariables and their itr

I'm sorry, I don't quite understand.

[Coronia]

if the variables are not supposed to be editted in the function, we'd better avoid using reference here. Namely LocalVariables, GlobalVariables and their itr

I'm sorry, I don't quite understand.

auto const& LocalVariables = ScenarioExt::Global()->Variables[false]; auto const& GlobalVariables = ScenarioExt::Global()->Variables[true]; I didn't notice any edit on these 2 variables in this pull request. It's just iterating them and reading their values, so maybe the reference sign & could be removed. Same for auto const& itr

[Fly-Star-him]

if the variables are not supposed to be editted in the function, we'd better avoid using reference here. Namely LocalVariables, GlobalVariables and their itr

I'm sorry, I don't quite understand.

auto const& LocalVariables = ScenarioExt::Global()->Variables[false]; auto const& GlobalVariables = ScenarioExt::Global()->Variables[true]; I didn't notice any edit on these 2 variables in this pull request. It's just iterating them and reading their values, so maybe the reference sign & could be removed. Same for auto const& itr

if the variables are not supposed to be editted in the function, we'd better avoid using reference here. Namely LocalVariables, GlobalVariables and their itr

I'm sorry, I don't quite understand.

auto const& LocalVariables = ScenarioExt::Global()->Variables[false]; auto const& GlobalVariables = ScenarioExt::Global()->Variables[true]; I didn't notice any edit on these 2 variables in this pull request. It's just iterating them and reading their values, so maybe the reference sign & could be removed. Same for auto const& itr

got it.

[github-actions[bot]]

Nightly build for this pull request:

• compiled-dll-b3d071e8279f91e776d64d5d6e8ecf47be84ab9e.zip These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.