Posted by: Thrake
« on: May 10, 2020, 09:22:08 AM »Quote from: skoormit link=topic=11316. msg131706#msg131706 date=1588909806Quote from: kks link=topic=11316. msg131663#msg131663 date=1588887650Quote from: skoormit link=topic=11316. msg131564#msg131564 date=1588866284Quote from: Thrake link=topic=11316. msg131541#msg131541 date=1588862161I started playing in older than 1. 9. 4 versions but still got 2 or 3 extra connections to Sol IIRC since I patched it. I feel like I also got more links beetween distant systems recently.
Keep in mind, the endpoints for a jp are calculated before you explore it.
I'm not sure if it is calculated when the jp is discovered, or when the system itself is created.
If these jps already existed before you patched to 1. 9. 5, but you only explored them after patching to 1. 9. 5, they could still be suffering from the bug.
Iirc this is not the case. The destination of an JP is determined when the JP is first explored, I think.
Negative. The database has information about both endpoints before the JP is explored.
I just tested this in a new game with SM, and the destination of JPs is definitely decided at the moment of exploration.
I suspect the confusing thing is that when playing a random stars game you'll always connect to a system that is given the next name on the list. My quick SM test randomly choose "US States" as the system naming theme, so the first JP I explored was always to a star named "Alabama. " The first time I tried this, the next JP in Sol connected to the bugged-out duplicate Sol. But when I reloaded the DB to try a second time, that same JP connected to "Alaska. "
This is a lot easier to see using known-stars. Actually, I save-scum* all the time in my known-stars game right before I explore a JP so that I can choose an interesting destination by saving/reloading.
* -- don't tell Steve
Well, something weird is going on, for sure.
I'm not confused by the same name being chosen.
The table in the database that contains jump point information already has that information before you explore the jp.
In fact, there is another table that holds the information about which races have explored which jps.
That said, if the jp is connecting to a new system, the system itself is not generated until you explore the jp.
If you are save scumming by re-exploring a jp that connects to a new system, you will see a different system every time, but each time the system number is the same.
It could also be the case that the examples I'm looking at are jps that have been explored by another race already. Therefore the endpoints have already been determined, they just aren't yet known to the humans.
At any rate, it appears that when Steve fixed the 1.9.4 bug that was causing JP links to known systems to instead create new systems with the same number, he inadvertently re-introduced the "all roads lead to Sol" bug.
We should be able to work around the bug by setting the local system generation chance to 100. That's not ideal, but it's good enough for me, for now.
Yes. I have at least 5 races paying a visit home before I even research trans-newtonian tech, and I was confused. Just SMed a new game where I met 6 races by 2028 and it turns out that I have 12 JP in Sol. All new games I played in the last version had the same issue (generation setting is set to minimum 3 JP in Sol). I guess there's no need to report it again if it's already a known issue