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.

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

Suggestion: danger level: system #10855

Open
ziproot opened this issue Dec 10, 2024 · 3 comments
Open

Suggestion: danger level: system #10855

ziproot opened this issue Dec 10, 2024 · 3 comments
Labels
enhancement Issues asking for or PRs making code changes that add new capabilities to the engine
Milestone

Comments

@ziproot
Copy link
Contributor

ziproot commented Dec 10, 2024

Problem Description

At the moment, the game checks the danger level for the system in order to compute the colors for the danger map and when calculating what path you should take to get from system A to system B. However, there is no way for missions and the like to access this data.

Related Issue Links

I can’t find any

Desired Solution

danger level: <system> that returns an integer value from 0 up, which is some measurement of your danger. 0 means no danger (green on the map), and higher numbers mean more danger.

Alternative Approaches

You could do something similar to what naev does, and have it instead be a number from 0 to 100 or 1000 that represents the proportion of ships that are hostile to the player, weighted by cost. Naev calculates only the “strongest faction,” but the idea of using how often a faction appears in a system is what naev does.

Additional Context

The most useful feature that this would enable is actually music, as if music adds the ability to check player conditions, it could also check the danger level, and play different music depending on how safe the system is. However, there is one coalition mission that has a different route than the player might take due to this danger level, so this might be useful here as well.
EDIT: Another place this could work is bounty missions, as this could let you not allow bounty missions in systems with no danger (as there would be no pirates). It would also mean no bounty missions if you are friendly with pirates, but that makes sense so I don’t think that’s an issue.

@TomGoodIdea TomGoodIdea added the enhancement Issues asking for or PRs making code changes that add new capabilities to the engine label Dec 10, 2024
@tibetiroka tibetiroka added this to the 0.10.11 milestone Dec 13, 2024
@tibetiroka
Copy link
Member

tibetiroka commented Dec 13, 2024

This would also be useful as an autocondition, getting the danger level of the system the player is currently in.

@ixPost
Copy link

ixPost commented Dec 19, 2024

You mean like escorting missions would be more likely in dangerous areas?

@ziproot
Copy link
Contributor Author

ziproot commented Dec 19, 2024

That could be another use case for it, definitely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issues asking for or PRs making code changes that add new capabilities to the engine
Projects
None yet
Development

No branches or pull requests

4 participants