Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Wrong selection of team members in transport missions #931

Closed
wzdev-ci opened this issue Sep 16, 2009 · 8 comments
Closed

Wrong selection of team members in transport missions #931

wzdev-ci opened this issue Sep 16, 2009 · 8 comments

Comments

@wzdev-ci
Copy link
Contributor

keyword_group keyword_select keyword_team keyword_transport resolution_wontfix type_bug | by Mohammad Ebrahim Mohammadi Panah <ebrahim@...>


In a regular mission create a team, for example team 1. From now on I call it "the old team 1".

In the following mission, which you are transported to another land, create some other machines and transport them. Now group your transported machines as team 1, "the new team 1". After that transport some of the old team 1 members.

Now if you hit key 1, only the new team 1 should be selected, but the old team 1 are also selected in addition.

Tested on Warzone2100 2.2.1 on Debian sid (warzone2100=2.2.1+dfsg1-1)


Issue migrated from trac:931 at 2022-04-15 19:15:11 -0700

@wzdev-ci
Copy link
Contributor Author

Ref commented


It's not a bug, it's a feature ;)
No, I'm actually using this "feature"...

@wzdev-ci
Copy link
Contributor Author

Per commented


How are you using this "feature"? I suspect it could cause "interesting" bugs.

@wzdev-ci
Copy link
Contributor Author

Zarel changed status from new to accepted

@wzdev-ci
Copy link
Contributor Author

Zarel set owner to Zarel

@wzdev-ci
Copy link
Contributor Author

Zarel commented


I think I know how to fix this.

@wzdev-ci
Copy link
Contributor Author

Emdek commented


I would say that this is feature, not a bug.

Also to which example errors it could lead?

@wzdev-ci
Copy link
Contributor Author

Per changed status from accepted to closed

@wzdev-ci
Copy link
Contributor Author

Per changed resolution from `` to wontfix

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant