Any Planet Start


Start on any of the first three planets: Vulcanus, Gleba, or Fulgora. Choose your planet in the startup mod settings before starting a new game. Now compatible with some modded planets!

Content
2 months ago
2.0
11.9K
Transportation Environment

b ✅ crash when enter game

3 months ago

模组加载失败:any-planet-start/asteroids.lua:87: attempt to index field '?' (a nil value)
stack traceback:
any-planet-start/asteroids.lua:87: in main chunk
[C]: in function 'require'
any-planet-start/data-updates.lua:45: in main chunk

3 months ago

Are you using any other mods that would have to do with asteroids? I'm unable to reproduce the issue.

3 months ago

No mod about that, but your 1.0.5 could be used with no crash.

3 months ago

Hey there,
Got the same issue, altho only if the startup setting is set to any other planet than Nauvis.

3 months ago

I still haven't been able to break it on my end. Are you using mods? What version of the game are you using it with, stable or experimental?

3 months ago

I use 2.0.28, with more than 200 mods... but none of them have to do with asteroids.

3 months ago

same problem. worked before update

3 months ago
(updated 3 months ago)

HOTFIX##

The issue occurs because some newly-added modded planets do not have asteroid_spawn_definitions in their connections (space-connection). When the script iterates over all space-connection prototypes, it encounters a connection without asteroid_spawn_definitions, causing a nil error on line 78.

A simple fix is to skip any connections that do not define asteroid_spawn_definitions (since only certain planets and connections require them). Insert this check right before calling map_definitions (around line 77) (asteroids.lua):

if connection == main_connection then
goto continue
end

-- Skip connections that don't have asteroid_spawn_definitions
if not connection.asteroid_spawn_definitions then
goto continue
end
This way, connections added by other mods that lack asteroid_spawn_definitions won't trigger an error when the script tries to run map_definitions(connection.asteroid_spawn_definitions).

3 months ago
(updated 3 months ago)

I already found the issue, I don't need a ChatGPT generated response to bugfix my mod for me. The problem is more complicated than that, and I've been working on a fix already. Line 78 isn't even the line where the error happens.

3 months ago

Can someone experiencing the issue post their mod list just so I can verify that it won't happen anymore?
Preferably in the form of an empty save file (just go into a new world and hit save) uploaded to somewhere like https://catbox.moe/ that way I can just click the sync button

3 months ago

I cannot access this website due to some internet policies in my country. Here is the website I uploaded.
https://wwkz.lanzouv.com/ipYyL2jhi6ib

2 months ago

Thank you, that confirmed the solution worked.
The issue was with the mod SLP - Dyson Sphere Reworked - my asteroid safety code was trying to modify modded space connections when it should only be working on vanilla space connections. I'm writing a much more generic asteroid safety script, but in the mean time this will do for now. Fixed in 1.1.5

New response