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

Sly & Gaia special - planet type cycling, colonization weighting #3001

Closed
rrobgill opened this issue Jun 3, 2020 · 4 comments
Closed

Sly & Gaia special - planet type cycling, colonization weighting #3001

rrobgill opened this issue Jun 3, 2020 · 4 comments
Labels
category:bug The Issue/PR describes or solves a perceived malfunction within the game. component:AI The Issue/PR deals with the Python AI decision making code or affects it. component:content scripting The Issue/PR deals with the FOCS language, turn events or the universe generator. status:resolved The Issue was resolved, either by answering properly or fixing the underlying bug.
Milestone
v0.4.10

Comments

@rrobgill
Copy link
Contributor

rrobgill commented Jun 3, 2020 •
edited by Vezzra

Description

Prevent planet types cycling when Sly inhabit a planet with Gaia special, and have AI devalue Gaia special when evaluating planets for Colonization

Gain

  1. At present the planet cycles through the planet types never stopping. Clearly Sly will never reach good suitability on a non-gaseous planet.

  2. When evaluating planets for Colonization, the AI presently treats a Gaia special as favorable for Sly, even though Sly receives no benefit from it.

Exobots also receive no benefit from Gaia specials, a Gaia special does not transform the planet type when inhabited by them, and the AI devalues the Gaia special when evaluating planets for Colonization.

Discussion

https://www.freeorion.org/forum/viewtopic.php?f=6&t=11685
@rrobgill rrobgill added the category:feature The Issue/PR describes or implements a new game feature. label Jun 3, 2020
@rrobgill rrobgill mentioned this issue Jun 3, 2020
Merged
@agrrr3
Copy link
Contributor

agrrr3 commented Jun 3, 2020

great catch!

@Vezzra
Copy link
Member

Vezzra commented Jun 7, 2020

That isn't a feature request, but a bug report. The current behavior should be considered a bug.

@Vezzra Vezzra added category:bug The Issue/PR describes or solves a perceived malfunction within the game. component:AI The Issue/PR deals with the Python AI decision making code or affects it. component:content scripting The Issue/PR deals with the FOCS language, turn events or the universe generator. and removed category:feature The Issue/PR describes or implements a new game feature. labels Jun 7, 2020
@Vezzra
Copy link
Member

Vezzra commented Jul 5, 2020

@rrobgill, with #3002 merged, can this be closed as resolved?

@rrobgill
Copy link
Contributor Author

rrobgill commented Jul 5, 2020

Yes, resolved by #3002

@rrobgill rrobgill closed this as completed Jul 5, 2020
@geoffthemedio geoffthemedio added the status:resolved The Issue was resolved, either by answering properly or fixing the underlying bug. label Jul 5, 2020
@Vezzra Vezzra added this to the v0.4.10 milestone Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category:bug The Issue/PR describes or solves a perceived malfunction within the game. component:AI The Issue/PR deals with the Python AI decision making code or affects it. component:content scripting The Issue/PR deals with the FOCS language, turn events or the universe generator. status:resolved The Issue was resolved, either by answering properly or fixing the underlying bug.
Projects
None yet
Milestone
v0.4.10
Development

No branches or pull requests
4 participants
@agrrr3 @Vezzra @geoffthemedio @rrobgill