"Master Of Bones" Milestone bugged

[Razy Racoon]

I only have the "Master Of Bones" Milestone left to complete and then I've finished the event. The problem is, that the milestone doesn't complete. I have all the bone parts but it doesn't trigger anything and it then disables the scanner to stop finding more bones. If I remove all collected bones I can re-scan and locate more to complete the milestone but again it doesn't trigger. Game reload hasn't helped. If anyone knows if this was fixed in the experimental update, I might try that to complete the expedition.

[Razy Racoon]

Opprinnelig skrevet av smurfy:

Opprinnelig skrevet av Razy Racoon:

{snip}. HG only need to change some of the game logic around the milestones to account for more possible combinations of completed milestones. I could try a new save. I dont do the expeditions on my main for these reasons lol

I've just been doing some testing in another expedition run to deliberately try and trigger issues, doing these milestones out of order, only visiting multiple dig sites in succession without completing bones collections, then using 1 collection of bones to mark off all of these milestones without building the fossil displays etc and could not break it.

At this point I'm out of ideas you can try. I'll keep it in mind in subsequent runs (I usually do each Expedition 5-10 times).
You could submit a zendesk ticket, and if they actively work on it they may ask for a copy of your save.

Yea I might enter a ticket if my new attempt fails. Anyone can watch my last two twitch streams where I was doing the event to see what I did exactly.

[Cles_fr]

Opprinnelig skrevet av Sk0rch:

Same problem.
Bones collected about 50 units in inventory.
Almost all expedition milestones completed.
"Master Of Bones" milestone (and similar ones starting from the first phase) does not activate the target indicator.

Yesterday after the update, "Excavation" milestones were automatically counted in all phases.

The dig office marker does not appear. If you arrive at the office via teleport, there is no manager in the office accepting/completing the task.

Same problem

[Razy Racoon]

I think I have figured out what has happened. My new game shows that I didnt even get to the final Dig site V. The planet is new and I dont recognise it. So somehow along the way, The game has marked off reach site V but because I didnt actually go there to get that waypoint, It wouldnt spawn for the Master of bones, to go back to.

[smurfy]

Opprinnelig skrevet av Razy Racoon:

I think I have figured out what has happened. My new game shows that I didnt even get to the final Dig site V. The planet is new and I dont recognise it. So somehow along the way, The game has marked off reach site V but because I didnt actually go there to get that waypoint, It wouldnt spawn for the Master of bones, to go back to.

Yes, that is the bug. Auto-completion of The Dig (reach the site) milestone(s). For some players, it marks off all 5, for others it's just been one or two. For you it was only #5.
It started last expedition and HG tried to fix it but to the best of my knowledge, the fix didn't work for most...
https://steamcommunity.com/app/275850/discussions/0/727997490786230711/

Experimental Branch 20/02

• Fixed an issue that prevent completion of the Chronicle expedition milestones if the Rendezvous milestones autocomplete.

https://www.nomanssky.com/2025/03/worlds-part-ii-5-58/

Bug Fixes

• Fixed an issue that prevents completion of the Chronicle expedition milestones if the Rendezvous milestones autocomplete.

This is why I tend to end up recommending the "set milestone(s) to optional" workaround, because I really don't have confidence that HG will be able to fix it.

There has been an increase in malicious multiplayer activity in Expeditions lately. The spawning of multiple Lost in Space derelict freighters on top of rendezvous POIs is the most notable.

I have my suspicions that this is also a multiplayer issue caused (deliberately or maybe even unintentionally?) by other players with mods/exploits but that's really hard to prove.
Purely playing with MP enabled hasn't triggered this auto-complete issue for me, yet. But that probably just means I haven't been in a session with a player that causes the issue.

[Razy Racoon]

Ah yea, Im surprised that I didn't realize I hadn't been to the final dig site yet and thought the 4th one was the final. That's why I asked if anyone knew the name of the system before.

To me when I was on multiplayer mode, there just seemed to be just way too many bases on planets, over 100, and too many players allowed to spawn at the digs, I think I had about 10 at one point. I could be wrong but all that stuff to load I assume was causing the long warp times, glitching reps and frame drops.
Thanks for the help Smurfy :)

[smurfy]

OK, some good/bad news.
Good News: I have got a save where the issue has occurred (Dig Sites 2-5 all auto-completed)
Bad News: it is a save on the Experimental Branch using the latest 2nd April patches, so it's not fixed in Experimental yet.

It is on a severely underpowered old laptop that I fired up for some other troubleshooting, and did occur after a couple of game crashes after the game tried to load (laptop PC related rather than game).

Will load that save on a decent machine and see if I can find any solutions better than an offline hack.

[smurfy]

Installed the Goatfungus save editor for the first time as nothing I tried in-game would help get around this issue.

Even manually reverting the auto-completed Dig Site milestones to not completed in the raw JSON with the save editor did not fix this issue. They all reverted back to auto-completed every time I re-loaded the edited save(s).

The only way I could get past it was to manually set all the affected subsequent Bone Collection milestones to completed.
That allowed me to claim their rewards when I loaded the save, as opposed to the isOptional method which makes those rewards unobtainable.

It's an option for players with the issue, but it's not one I particularly like to recommend.

[Rexxer]

Five times you must do this: go visit the Gek Paleo Society NPC-nerd at a Rendezvous. When you agree to help him, you will become his assistant and get a milestone for that AND you get a specific blueprint for a specific fossil jig. There are 5 jigs and you must remember which one is the one the last Gek gave you, because that is the only one that will advance the quest. You have to use the fossil jig to assemble a full skeleton. And use the right one. By the 5th Gek, it can get confusing if you aren't reading what they are saying, and if you use the wrong one, nothing will happen.

[smurfy]

Opprinnelig skrevet av Rexxer:

Five times you must do this: go visit the Gek Paleo Society NPC-nerd at a Rendezvous. When you agree to help him, you will become his assistant and get a milestone for that AND you get a specific blueprint for a specific fossil jig. There are 5 jigs and you must remember which one is the one the last Gek gave you, because that is the only one that will advance the quest. You have to use the fossil jig to assemble a full skeleton. And use the right one. By the 5th Gek, it can get confusing if you aren't reading what they are saying, and if you use the wrong one, nothing will happen.

Clearly you have no clue about the autocomplete bug that has impacted multiple players in that and the previous expedition.
The save file I just replicated it in is 20 minutes old. It has not left the starter planet.
The Milestones for arriving at Dig Site 2, 3, 4 & 5 are all marked as done, so I will never get directions to those sites.

Examples - Titan:
1. Since the 5.58 patch:

• Expedition chronicles 2 not working
  
• Rendezvous auto completed
  
• Notes Note Notes - Reply 37 here was the 1st I saw that claimed it didn't fix it

2. Before the 5.58 patch:

• rendevous auto complete cant finish the quests
  
• Expedition help.
  
• %Planet% Titan Expidition Killer Bug?
  
• Titan Expedition - Rendezvous Points
  
• Titan rendezvous bugged - cant proceed
  
• Expedition 17 Massively Bugged
  
• Problem rendezvous points expedition

Examples - Relics:

• expedition tasks bugged
  
• "Collect a Complete Fossil" tasks are bugged.
  
• The dig site 3 does not appear.
  
• Cannot complete "Associate Field Agent" for dig site 2. cannot locate digsite 2. All digsite auto completed as well
  
• Several responders in the Experimental thread(s) and the Relics announcement thread also reported it without having their own topics

[Bri's Wacky Gaming]

Im stuck on all the field agent milestones, so phase 2 to 5, nothing i did fixes it and all the npc does is try to teach me their language , have been for a week now :(

[smurfy]

Opprinnelig skrevet av Bri's Wacky Gaming:

Im stuck on all the field agent milestones, so phase 2 to 5, nothing i did fixes it and all the npc does is try to teach me their language , have been for a week now :(

If your milestones haven't auto-completed, your post is off-topic here and you need to start your own thread.

Opprinnelig skrevet av Bri's Wacky Gaming:

havent seen any fixes for this yet, as this happened to me everything is completed except for the field agent hand ins for phase 2-5 :(

The 2nd milestones do not require talking to the Gek, you just need to get back to the Dig Site, but if your Dig Site milestones autocompleted, then getting to the right site will not help.

You will have a few options:
1. Leave the Expedition open and hope HG come up with a working patch.
2. If the Expedition is being run as a brand new save, just delete it and start again (turn MP off to hopefully avoid this bug). If it is an existing save, return to the main save and refer to option #1.
3. Implement a manual workaround to make the bugged milestone(s) optional and complete the Expedition. See reply 13 on page 1 here.
4. Use a save editor to mark the hand-in milestones as completed (see reply #22 above)

[Rexxer]

Opprinnelig skrevet av smurfy:

Opprinnelig skrevet av Rexxer:

Five times you must do this: go visit the Gek Paleo Society NPC-nerd at a Rendezvous. When you agree to help him, you will become his assistant and get a milestone for that AND you get a specific blueprint for a specific fossil jig. There are 5 jigs and you must remember which one is the one the last Gek gave you, because that is the only one that will advance the quest. You have to use the fossil jig to assemble a full skeleton. And use the right one. By the 5th Gek, it can get confusing if you aren't reading what they are saying, and if you use the wrong one, nothing will happen.

Clearly you have no clue about the autocomplete bug that has impacted multiple players in that and the previous expedition.
...

• Several responders in the Experimental thread(s) and the Relics announcement thread also reported it without having their own topics

I just completed Relics myself, no issues. Ground through it mostly in one session. I did notice at Ren 5 my play file started to corrupt (flickering, variable names in dialogue instead of quest names, no reported restore point or autosave), but I restarted the game, being very careful not to save it before restarting, and it was fine. That's the only thing I've noted about recent play through is that after a long while there's some internal corruption that can occur. Lots of weird stuff happens. At one point I was building a base, on land no water around, and everything suddenly went black and the screen recorded I was 900 u below sea level and I could hear water sounds. I tried swimming up but everything stayed black, although the sounds were consistent with me being in the game. I reloaded the game and it still was blacked out outside of the base, and inside the base it was grey:
https://steamcommunity.com/sharedfiles/filedetails/?id=3457252742
The only solution was to completely restart the game.
My guess is that similar corruption is occurring on other platforms with longer play times, such as in Expedition play, but possibly with just the issues described. Probably some internal memory scratch pads are being reused without clearing or something like that.

[smurfy]

Opprinnelig skrevet av Rexxer:

I just completed Relics myself, no issues. Ground through it mostly in one session. I did notice at Ren 5 my play file started to corrupt (flickering, variable names in dialogue instead of quest names, no reported restore point or autosave), but I restarted the game, being very careful not to save it before restarting, and it was fine. That's the only thing I've noted about recent play through is that after a long while there's some internal corruption that can occur. Lots of weird stuff happens. At one point I was building a base, on land no water around, and everything suddenly went black and the screen recorded I was 900 u below sea level and I could hear water sounds. I tried swimming up but everything stayed black, although the sounds were consistent with me being in the game. I reloaded the game and it still was blacked out outside of the base, and inside the base it was grey:
https://steamcommunity.com/sharedfiles/filedetails/?id=3457252742
The only solution was to completely restart the game.
My guess is that similar corruption is occurring on other platforms with longer play times, such as in Expedition play, but possibly with just the issues described. Probably some internal memory scratch pads are being reused without clearing or something like that.

I've completed it 3 times already, and started another 3 or 4 times.

Opprinnelig skrevet av me:

The save file I just replicated it in is 20 minutes old. It has not left the starter planet.

I had been trying to trigger this bug for a while (as I mentioned in several other threads linked above). I now suspect it is due to any sort of crash that occurs as the game is doing an autosave.
I'm trying to re-trigger it again to see if I can do it on demand. Then I will send my findings and the data to Zendesk with the corrupted save files. As shown above, HG acknowledged the issue was present in Titan Expedition and published an ineffective fix in 5.58.

[Rexxer]

Opprinnelig skrevet av smurfy:

I had been trying to trigger this bug for a while (as I mentioned in several other threads linked above). I now suspect it is due to any sort of crash that occurs as the game is doing an autosave.

I'd agree an autosave interruption might be an associated trigger, given how often autosaves in the past have been linked with similar issues. However, it still stands in my games at least, the crash or corruption only occurs after playing a long while. I just remembered another event which was a similar corruption/crash which happened shortly after Worlds II dropped, but at that point there was not enough track record to indicate a pattern. Now there is.
The first weird corruption occurred while jumping galaxies. In one jump, I ended up deep under the surface, similar to the recent -900 u event with the grey screen, and then when my avatar was pushed to the surface, my crashed ship spawned directly under my avatar, (not in a crash zone 500+ u away as is normal):
https://steamcommunity.com/sharedfiles/filedetails/?id=3441858071
https://steamcommunity.com/sharedfiles/filedetails/?id=3441862357
And then in Relics at R5, the corruption of dialogue boxes and other routines such as the save modules.
And as already shown, the -900 u plunge into darkness followed by a reload which did not clear the error, just simply placed my character in another corrupted area of the map where the last save was:
https://steamcommunity.com/sharedfiles/filedetails/?id=3457252742
I can pretty clearly see all of these events are related as they never ever occurred prior to Worlds II, and in my game they all occurred after a few hours of play. Reloading could not fix these issues, only restarting NMS whole allowed a reset of the game to playable state.
There were a couple other similar crashes/corruptions under similar circumstances early enough on so I hadn't noticed a pattern and therefore didn't bother to document the weirdness.

[smurfy]

Just keep doubling down on the irrelevance don't you.