Stellaris

Stellaris

Exotic Deposits and Resources
 This topic has been pinned, so it's probably important
Lord and savior, DaddyGaylord  [developer] 22 Mar, 2023 @ 12:03pm
Bugs
If you find any bugs (wither in-game or in the code) then you can report it here
< >
Showing 1-12 of 12 comments
Chaos Rocker 1 Apr, 2023 @ 6:27am 
Hi,

getting game crashes around mid game time and the last error lines are as below

[trigger_impl.cpp:1192]: Script Error: Invalid context switch [owner] from Jezemei IVa [planet], file: common/deposits/exotic_deposits.txt line: 906, Scope:
type=planet
id=6747
random={ 0 17561869 }
random_allowed=yes

Getting tons of invalid context switch for various planets like this...pls help out

Thanks in advance
Inny 3 Apr, 2023 @ 11:26am 
If you check for the owner of a planet, you must first check if the owner exists in the first place with exists = owner.
Happyperson3796 3 Apr, 2023 @ 12:32pm 
getting
[13:51:25][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 105
and invalid context switch errors. My game also started crashing around 2290.
Chaos Rocker 4 Apr, 2023 @ 4:01am 
Originally posted by Inny The Merger:
If you check for the owner of a planet, you must first check if the owner exists in the first place with exists = owner.

I am not manually checking the owner...does it mean when i am selecting my planets? Also how to check exists = owner thing you mentioned?
Lord and savior, DaddyGaylord  [developer] 4 Apr, 2023 @ 9:04am 
I'll fix them soon

Ok should be fixed
Last edited by Lord and savior, DaddyGaylord; 4 Apr, 2023 @ 9:28am
Chaos Rocker 5 Apr, 2023 @ 12:44pm 
Thanks Mate....really loving your mod....i'll play with the latest update and let you know if i am still encountering any bugs
Chaos Rocker 6 Apr, 2023 @ 11:01am 
Originally posted by experiencerocker7:
Thanks Mate....really loving your mod....i'll play with the latest update and let you know if i am still encountering any bugs
Facing the same error still dude....
Lord and savior, DaddyGaylord  [developer] 6 Apr, 2023 @ 2:01pm 
Ok m8 try it now
Happyperson3796 7 Apr, 2023 @ 5:04pm 
My game still crashes using this mod
Lord and savior, DaddyGaylord  [developer] 8 Apr, 2023 @ 4:23am 
Could you send me your error log?

Ok what about now? I removed the event entirely and used some simpler methods
Last edited by Lord and savior, DaddyGaylord; 8 Apr, 2023 @ 6:35am
Happyperson3796 8 Apr, 2023 @ 1:24pm 
this and your mod Buildings and districts overhaul are still crashing. Here's the parts of my error log that mention this mod:

[16:16:27][effect.cpp:417]: Error: "Unexpected token: army_type, near line: 32
" in file: "events/exodep_events.txt" near line: 33
[16:16:27][effect_impl.cpp:647]: variable effect at file: events/exodep_events.txt line: 34 accepts only yes or no as values
[16:16:27][persistent.cpp:46]: Error: "Unexpected token: else, near line: 37
" in file: "events/exodep_events.txt" near line: 39
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 43
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - = in events/exodep_events.txtline: 43
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - id in events/exodep_events.txtline: 44
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - hide_window in events/exodep_events.txtline: 45
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - is_triggered_only in events/exodep_events.txtline: 46
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - immediate in events/exodep_events.txtline: 47
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - if in events/exodep_events.txtline: 48
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - limit in events/exodep_events.txtline: 49
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - any_planet_within_border in events/exodep_events.txtline: 50
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - has_active_building in events/exodep_events.txtline: 51
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 53
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - set_variable in events/exodep_events.txtline: 54
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - which in events/exodep_events.txtline: 55
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - value in events/exodep_events.txtline: 56
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 58
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - = in events/exodep_events.txtline: 58
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - trigger in events/exodep_events.txtline: 59
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - parameters in events/exodep_events.txtline: 60
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - army_type in events/exodep_events.txtline: 61
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 63
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - = in events/exodep_events.txtline: 63
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 65
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - else in events/exodep_events.txtline: 66
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - clear_variable in events/exodep_events.txtline: 67
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 69
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 72
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - = in events/exodep_events.txtline: 72
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - id in events/exodep_events.txtline: 73
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - hide_window in events/exodep_events.txtline: 74
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - is_triggered_only in events/exodep_events.txtline: 75
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - immediate in events/exodep_events.txtline: 76
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - if in events/exodep_events.txtline: 77
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - limit in events/exodep_events.txtline: 78
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - any_planet_within_border in events/exodep_events.txtline: 79
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - has_active_building in events/exodep_events.txtline: 80
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 82
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - set_variable in events/exodep_events.txtline: 83
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - which in events/exodep_events.txtline: 84
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - value in events/exodep_events.txtline: 85
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 87
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - = in events/exodep_events.txtline: 87
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - trigger in events/exodep_events.txtline: 88
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - parameters in events/exodep_events.txtline: 89
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - army_type in events/exodep_events.txtline: 90
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 92
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - = in events/exodep_events.txtline: 92
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 94
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - else in events/exodep_events.txtline: 95
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - clear_variable in events/exodep_events.txtline: 96
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 98
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
[16:16:27][eventmanager.cpp:421]: Corrupt Event Table Entry - } in events/exodep_events.txtline: 99
This usually means the syntax is wrong earlier in the file (e.g. wrong number of { or }, non-existent curly brackets effects)
Lord and savior, DaddyGaylord  [developer] 8 Apr, 2023 @ 1:26pm 
Yeah I removed the events, should be fine now
< >
Showing 1-12 of 12 comments
Per page: 1530 50