When your SE game gets really slow, you have to clean out the mothballs and see what happens. 1000 floating armor blocks aren't healthy. Those steel plates you dropped? still there. So I load my save in this program and then select all the "junk" I want to get rid of. Trim it down to the ships I want, instead of floating chunks and plates I dropped when the inventory was full. Game run out of ID's? Just trash a few thousand of them... I suppose you can also use it to recover from space disasters. Like when I saved with 2 merge blocks close to each other. Then I loaded and my ship exploded because somehow the merge blocks suddenly merged when the game was loaded. Solution? delete the merge blocks from the save game. Floating ore chunks/stones...etc etc. I guess if you wanted you can delete the enemies guns.
Well, once you load the save, it goes into the xml and displays all the grids you can interact with, including planets and asteroids you have been mining. If you rmb on one of them you can select "properties" to open the tree, or if you click on the root you can view info about the number of grids and the tree items. Select delete and the grid or item you have selected will be deleted. It can delete anything with an entityID. Also, if you select multiple items, it will delete them all, but only the grids, not individual parts of a ship. Those can only be deleted one by one. Then, you can save over your game, then reload it and enjoy the fact you won't run into a floating stone during that next outing. or floating items inside your large ship.. they can cause damage. Oh, you can't delete asteroids or planets.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hrrrm you know, the windows build under windows 10 doesn't produce newline characters in the xml. Really strange, but I'll see if it's some component from the windows 7 that I included in the build, is casuing a problem. Only thing is, I don't have a windows 10 build or a vm. I suppose the easiest solution is a vm running different windows versions. Perhaps the word easiest needs quotes hah hah
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made this program to keep your SE save game spotless and shiny clean.
When your SE game gets really slow, you have to clean out the mothballs and see what happens. 1000 floating armor blocks aren't healthy. Those steel plates you dropped? still there. So I load my save in this program and then select all the "junk" I want to get rid of. Trim it down to the ships I want, instead of floating chunks and plates I dropped when the inventory was full. Game run out of ID's? Just trash a few thousand of them... I suppose you can also use it to recover from space disasters. Like when I saved with 2 merge blocks close to each other. Then I loaded and my ship exploded because somehow the merge blocks suddenly merged when the game was loaded. Solution? delete the merge blocks from the save game. Floating ore chunks/stones...etc etc. I guess if you wanted you can delete the enemies guns.
Well, once you load the save, it goes into the xml and displays all the grids you can interact with, including planets and asteroids you have been mining. If you rmb on one of them you can select "properties" to open the tree, or if you click on the root you can view info about the number of grids and the tree items. Select delete and the grid or item you have selected will be deleted. It can delete anything with an entityID. Also, if you select multiple items, it will delete them all, but only the grids, not individual parts of a ship. Those can only be deleted one by one. Then, you can save over your game, then reload it and enjoy the fact you won't run into a floating stone during that next outing. or floating items inside your large ship.. they can cause damage. Oh, you can't delete asteroids or planets.
hrrrm you know, the windows build under windows 10 doesn't produce newline characters in the xml. Really strange, but I'll see if it's some component from the windows 7 that I included in the build, is casuing a problem. Only thing is, I don't have a windows 10 build or a vm. I suppose the easiest solution is a vm running different windows versions. Perhaps the word easiest needs quotes hah hah