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

Calculate step sizes #13

Open
IanMayo opened this issue Mar 8, 2019 · 2 comments
Open

Calculate step sizes #13

IanMayo opened this issue Mar 8, 2019 · 2 comments
Assignees

Comments

@IanMayo
Copy link
Collaborator

IanMayo commented Mar 8, 2019

I haven't had this verified yet, but I've had a go at calculating the time it takes to travel one cell at different speeds:
https://docs.google.com/spreadsheets/d/1-cpAmVd17EUoviF4f3cprWcBYMbqiJVuSc8jSHZXWDw/edit#gid=0

Snapshot here:
image

The time/cell row indicates how many hours it takes to travel one cell at that speed

This would mean a slight change to your map stepping logic. A player has a time allowance that he's planning for (e.g. 24 hours). Once the speed is set/changed, the entry in the time/cell row for that speed shows how much time it takes to travel one cell. So, they're either building up to the value of 24, or their consuming what's left of the 24 hour budget.

So, a ship travelling a 9 kts will take 4 hours per cell. So, given a starting budget of 24 hours, each click will consume 4 hours of that.

I don't think the d3 end needs that lookup table. It's just the speed in kts divided by the cell diameter.

@BMPMS
Copy link
Collaborator

BMPMS commented Mar 8, 2019 via email

@BMPMS
Copy link
Collaborator

BMPMS commented Mar 11, 2019

Again, not sure where we are here. As you can see above I'm keen to keep all these calculations away from the d3 side for extra flexibility.

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

No branches or pull requests

2 participants