Equidistant part of slice?

[Chosi128]

Maybe this is not an issue but how or why is the the left equidistant, which is attached to your slice for map building purposes, but which is - in my logic - not part of your slice (since it's an equidistant and you are by no means entitled to it) calculated into the values of your slice? Not sure what would be a good way to improve this, which is not an overkill, but right now it simply reduces the value of the information below the slices, since you have to manually verify or redo the math, if you don't consider the equidistant part of your slice.

[shenanigans-be]

What you're touching on is really an issue with the underlying idea of the Milty draft itself, and it boils down to: You're not really entitled to any part of "your" slice. "Having a slice" is just a convenience that players kind of implicitly agree on, but the slices are just really a way to build a map where you can influence how many resources are near your home system, but that comes with no real guarantees either way.

That being said: checking the slice's values without equidistants is math that a lot of people do in their heads anyway, so I might consider adding some UI thing that enables that.. Give me some time to think about it 😅

[Chosi128]

Thanks for the explanation and considering this. I did miss out on the opportunity to also appreciate your work earlier, so let me make a donation in the meantime!

[Chosi128]

I put some more time to this and clarified my thoughts a bit more. Let me add this to my post for clarity:

I think your slices defines itself by what is closer to you than to anyone else, so it does not belong to you (nothing does) but you have the best access to it and can probably defend it best. Following that logic the equidistants are not part of your slice.

I think what Milthy Draft does is attaching one ED to each slice to avoid a complicated second step of selecting or inserting random EDs into the map. This keeps things simple while making the EDs a strategic part of the draft (instead of adding them at random later for example). But I am not sure this actually makes them a part of your slice. If I check https://conclave.mistake-not.net/ or other tools, they don't add EDs to a slice either.

The reason I bring this here is not just because I need to do more math in my head when checking the slices, that would be fine, but if you follow the above logic for what's your slice, the parameters I can set in your site (minimum optional value etc) "don't work", because for some slices all of that value is in your actual slice, and for some of them that value includes your ED, so "outside" your slice (in the above view of a slice).

I am very thankful for your site and your work! Right now we simply regenerate slices until al/most of them have their value without the ED and that's an acceptable workaround for now.

[shenanigans-be]

I definitely see your point! The issue is always finding a balance between "being able to configure and adjust everything" and "having an easy-to-use and clear interface". I can imagine having some "calculate slice values with/without ED"-toggle in the advanced settings somewhere, but then I'm not sure how to make that difference visually clear in the draft itself.

I'll keep it in mind next time I'm tinkering with this :)

[Chosi128]

I absolutely agree with the aspect of simplicity and not covering for all edge cases. Awareness and consideration is all I needed, so thank you!

[mprischink]

I‘d also love to have the ED info separated somehow, like slice values without ED in brackets next to the values with ED, or the ED values separated. For the map generation settings, I can see, that one would want the EDs not included for lower and upper bounds calculations (our group only did default values so far), so a flag to toggle the inclusion of EDs in the generation calculations as suggested makes sense. Anyways, great work!