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

The game assume the uniqueness of "canrecruit=yes" in each side. #3168

Closed
yifan92 opened this issue May 24, 2018 · 6 comments
Closed

The game assume the uniqueness of "canrecruit=yes" in each side. #3168

yifan92 opened this issue May 24, 2018 · 6 comments
Labels
Invalid Issues that do not belong in this tracker or do not actually exist. Needs more info Issues deemed to contain insufficient information for reproducing or fixing.

Comments

@yifan92
Copy link

yifan92 commented May 24, 2018

If a second unit with "canrecruit=yes" is deployed with [unit] tag, it would simply fail. Examples include the 1st scenario of UMC campaign The Final Exam, and Lethalia in LotI.
@ProditorMagnus
Copy link
Contributor

Creating multiple units with canrecruit=yes works for me.

@yifan92
Copy link
Author

yifan92 commented May 24, 2018

The bug occurs when you create a unit at the start of a scenario with WML.

@gfgtdf
Copy link
Contributor

gfgtdf commented May 24, 2018

this still sounds very unlikely and we will not debug The Final Exam or LotI. Maybe you could post a a minimal test case for reproducing?

@sevu sevu added the Needs more info Issues deemed to contain insufficient information for reproducing or fixing. label May 24, 2018
@yifan92
Copy link
Author

yifan92 commented May 24, 2018 •
edited

The Final Exam example is a simple test case. By default, you should start the 1st scenario with a Bowman named Johnny but you don't. And if you go to the code and comment out the "canrecruit=yes" line in the prestart event, he appears.

The same code is bug-free in 1.12.

@yifan92
Copy link
Author

yifan92 commented May 24, 2018

Seems that it's caused by conflict with UMC mod.

@yifan92 yifan92 closed this as completed May 24, 2018
@sevu sevu added the Invalid Issues that do not belong in this tracker or do not actually exist. label May 24, 2018
@Konrad22
Copy link
Contributor

Which UMC mod?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Invalid Issues that do not belong in this tracker or do not actually exist. Needs more info Issues deemed to contain insufficient information for reproducing or fixing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@gfgtdf @ProditorMagnus @sevu @yifan92 @Konrad22