Nato Tree Topper and objet drop

[Kaorru87]

Hello i drop Nato Tree Topper and another tropper is would know if is exist command for give item because i have drop and dont remember where i have drop

[pha]

Hello, I'm not sure which topper you mean, is it the Festive tree topper? If so then the only way is to reload the previous save where you had the object. This goes for most objects, but the objects that are necessary for quest progressions have commands enabled to spawn them, like the Broken Banana topper for instance.

Is the Banana Topper one of the ones you lost? If it is then you can open the command window by hitting the Tilde key "|" five times rapidly, then write the following line and press enter:
spawn.flatpack Topper_Broken_Banana

After escaping the command window, the topper flatpack should be in front of you.

If it's other objects then that, you can try to load a previous save like this, and the order is important:

1. First disconnect from the internet. (Otherwise steam cloud will mess this up)

2. Open the "Fruitbus Save data" folder. Located usually here: C:\Users\Username\AppData\LocalLow\Krillbite\Fruitbus

3. If you have trouble finding the files, you may have to enable “Show Hidden Items” in the folder settings, since the “AppData” folder is usually hidden.

4. Inside the “Fruitbus Save Data” folder will be one or more folders called "Slot1", "Slot2" etc, a "Manifest.Json" file and "steam_autocloud.vdf" file. Delete the "steam_autocloud.vdf" file. This will be remade once you sync with steam cloud again after, so don't worry.

5. Open the slot folder of the save you are using and want to recover. Usually "Slot1", but the same goes for other slots. Open the "Save1" folder inside there, and you will see a folder called "Backups", a bunch of .json files and a screenshot image. These are the files that keep track of every system in your save, and the screenshot was taken at the time the save was made, so while you browse save files, the screenshot can help you find the save you are looking for.

6. If you want to make 100% sure you don't loose the current save files then you should back these up by copying them to a different location on your pc. (It’s not a bad idea to back up the entire “Fruitbus Save Data” Folder)

7. Open the "Backups" folder within the “Save1” Folder. In there should be a few folders with backup saves that are just named for the date and time those saves where made, and inside they should have the same type of files you found in the root "Save1" folder.

8. Find a save that looks good based on the screenshot, or if it's hard to tell, you can just try them out.

9. Select all the files within the folder you want to use, and copy them.

10. Return to the root "Save1" folder, and delete the .json files and the screenshot. NOT the "Backups" folder, that is VERY important.

11. Paste in the files you copied from the backup folder.

12. Now, while still offline, you can launch the game.

13. You will see a message from Steam saying: "! Unable to sync... If you play now, you may not have previous game progress and you may permanently lose it". Choose "Play anyway".

14. Continue the game from the save you edited, and check if everything is working as intended.

15. If the issue is still there, exit the game and try other saves from the Backups folder, until you find a save where the issue is gone.

16. Once you have confirmed that everything is working as it should, save the game.

17. Reconnect to the internet. You can stay in the game or exit while you do so.

18. Once you've exited the game and internet is reconnected, the Steam page for the game should say there is a cloud conflict or cloud out of sync (it may also start trying to up/download automatically): Click the Cloud status and choose Local Save (or sync if that's the only option).

19. Then wait for the files to finish uploading/syncing, and start the game to see if everything is still fine.

If this doesn’t help you, please let us know in our Discord (https://discord.gg/xCY82tSD), which is the only place we can send Saves and log files back and forth to diagnose and fix the issue for you.