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

encounters re-work #107

Open
7yl4r opened this issue May 21, 2015 · 1 comment
Open

encounters re-work #107

7yl4r opened this issue May 21, 2015 · 1 comment

Comments

@7yl4r
Copy link
Owner

7yl4r commented May 21, 2015

The number of events encountered in this game is most definitely unrealistic, my thinking is that encounters should actually be chances to deviate course to encounter a detected object later. You can see this a bit in the debris encounter, where you can choose to bypass or rendezvous with the object.

However, when you're flying by objects in the travel screen it feels more like you're bumping into things. So here is my idea to make things better fit the real world:

Object-encounter icons get replaced by course-deviation nodes (similar to maneuver nodes (which are still appearance-only 😢))
or-traj-mockup

Upon arriving at this node you can choose to rendezvous based on your scanner's information on the event or continue on course. Thus, you have to take a calculated risk to rendezvous or not. Choosing to rendezvous has some fuel cost and may slow your progression to your destination (next station is farther), but may also payoff bigtime in scrap/fuel/whatever. After choosing to rendezvous, the actual event sprite will be placed off-screen so that you will approach it and trigger the interaction.

This will make people "gamble" in the game more, will make players feel like they have more control over the ship's path, and will bring more mystery and allure surrounding the events. In short, I think it will make the game more fun. What do you guys think?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/16337804-encounters-re-work?utm_campaign=plugin&utm_content=tracker%2F13859664&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F13859664&utm_medium=issues&utm_source=github).
@terpin
Copy link
Collaborator

terpin commented May 21, 2015

Definitely adds more depth to the game!

On Wed, May 20, 2015 at 9:17 PM, Tylar [email protected] wrote:

The number of events encountered in this game is most definitely
unrealistic, my thinking is that encounters should actually be chances to
deviate course to encounter a detected object later. You can see this a bit
in the debris encounter, where you can choose to bypass or rendezvous with
the object.

However, when you're flying by objects in the travel screen it feels more
like you're bumping into things. So here is my idea to make things better
fit the real world:

Object-encounter icons get replaced by course-deviation nodes (similar to
maneuver nodes (which are still appearance-only [image: 😢]))
[image: or-traj-mockup]
https://cloud.githubusercontent.com/assets/1051390/7740226/1a350156-ff3c-11e4-8994-655cf6c65d5a.png

Upon arriving at this node you can choose to rendezvous based on your
scanner's information on the event or continue on course. Thus, you have to
take a calculated risk to rendezvous or not. Choosing to rendezvous has
some fuel cost and may slow your progression to your destination (next
station is farther), but may also payoff bigtime in scrap/fuel/whatever.
After choosing to rendezvous, the actual event sprite will be placed
off-screen so that you will approach it and trigger the interaction.

This will make people "gamble" in the game more, will make players feel
like they have more control over the ship's path, and will bring more
mystery and allure surrounding the events. In short, I think it will make
the game more fun. What do you guys think?


Reply to this email directly or view it on GitHub
#107.

@7yl4r 7yl4r added this to the 2.X polishes milestone Sep 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants