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

Cache interior spawn positions & optimise search algorythm #1063

Open
parar020100 opened this issue Mar 9, 2024 · 4 comments
Open

Cache interior spawn positions & optimise search algorythm #1063

parar020100 opened this issue Mar 9, 2024 · 4 comments

Comments

@parar020100
Copy link
Collaborator

I've been considering this one for a while now
Interior spawning freezes the game even with the use of subroutines
I was wondering whether with the new (rectangle) way of specifying interior size we could save a number of found interior positions per each map to reduce the search time

@parar020100 parar020100 changed the title Cache interior spawn positions Cache interior spawn positions & optimise search algorythm Mar 9, 2024
@MattJeanes
Copy link
Owner

We could cache interior positions for a particular interior size yes, I think trying to deviate from that though could get complicated and potentially buggy. That said, what if it spawns in a bad place? We can't always detect this programmatically so caching/saving these positions could be bad. Right now, they can just re-roll the dice by respawning it.

@parar020100
Copy link
Collaborator Author

parar020100 commented Mar 11, 2024

That said, what if it spawns in a bad place?

We could add some way to mark a bad interior position as well
As well as a way to toggle random positioning

@parar020100
Copy link
Collaborator Author

The obvious downside is people not knowing about the "bad position" button
As one of the solutions, position caching could be an off-by-default setting
Those who know about it would be able to enable it and get faster game experience

@MattJeanes
Copy link
Owner

The problem with an off-by-default setting though is that barely anyone will know about that too and you must question if it is worth the development effort at that point. I'd love to see faster spawning but I am not sure how we can effectively solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New
Development

No branches or pull requests

2 participants