Home Creators Posts Import Register Favorites Logout

Content

Hi,

here are two important patches for V240_022. One fixes an error at boarding the ship while the other fixes the autotrain dialogue with Nimhe which may block progression

PATCH 1 - Boarding PatchCopy file 810_location_support.rpy into folder 800_locationsOnly for version V240_022

PATCH 2 - Nimhe dialogue block autotrainercopy file 620_interact_nimhe.rpy into folder 600_interactonly compatible with V240_022

I'll address some other minor consistency issues over the weekend before I prepare the Offical Subscriber Release for 25th Feb. Thanks for patrons who reported these issues.y.v.

Files

Comments

Herra Sebaot

Boarding the ship still seems to crash the game... Installed both patches, but no change.

y.v.

I am 100% certain that the relevant PATCH 1 is working. Can you post the error message in the chat channel or on discord? Also, did you copy the files into the correct folders (below the folder called "game"!) or they are just ineffective and not used... If you get an overwrite warning when copying the patches there you are in the right spot/folder

y.v.

Also, these work only with exact version 240_022. They will guaranteed crash the game if used in any other version.

Herra Sebaot

I copied it to folder: D:\Games\SpaceJourneyX-240_022-pc\SpaceJourneyX-240_022-pc\game\800_locations it did have a file with same name before. I renamed that to 810_location_supportOLD.rpy There also is a file named 810_location_support.rpyc. Error message looks like this: [code] I'm sorry, but an uncaught exception occurred. While running game code: File "game/03_GAME.rpy", line 243, in script call call sandbox_interior() from _call_sandbox_interior File "game/500_navigator/552_sandbox_interior.rpy", line 779, in script call call boarding() from _call_boarding File "game/800_locations/810_location_supportOLD.rpy", line 11, in script call call intercept_exit("LOCCargo") from _call_intercept_exit File "game/03_GAME.rpy", line 243, in script call call sandbox_interior() from _call_sandbox_interior File "game/500_navigator/552_sandbox_interior.rpy", line 779, in script call call boarding() from _call_boarding File "game/800_locations/810_location_supportOLD.rpy", line 11, in script call call intercept_exit("LOCCargo") from _call_intercept_exit ScriptError: could not find label 'intercept_exit'. -- Full Traceback ------------------------------------------------------------ Full traceback: File "game/03_GAME.rpy", line 243, in script call call sandbox_interior() from _call_sandbox_interior File "game/500_navigator/552_sandbox_interior.rpy", line 779, in script call call boarding() from _call_boarding File "game/800_locations/810_location_supportOLD.rpy", line 11, in script call call intercept_exit("LOCCargo") from _call_intercept_exit File "D:\TALSI\Special\Games\SpaceJourneyX-240_022-pc\SpaceJourneyX-240_022-pc\renpy\ast.py", line 1414, in execute rv = renpy.game.context().call(label, return_site=self.next.name) File "game/03_GAME.rpy", line 243, in script call call sandbox_interior() from _call_sandbox_interior File "game/500_navigator/552_sandbox_interior.rpy", line 779, in script call call boarding() from _call_boarding File "game/800_locations/810_location_supportOLD.rpy", line 11, in script call call intercept_exit("LOCCargo") from _call_intercept_exit File "D:\TALSI\Special\Games\SpaceJourneyX-240_022-pc\SpaceJourneyX-240_022-pc\renpy\script.py", line 1103, in lookup raise ScriptError("could not find label '%s'." % str(original)) ScriptError: could not find label 'intercept_exit'. Windows-10-10.0.26200 AMD64 Ren'Py 8.3.3.24111502 Space Journey X 240_022 Sat Feb 21 19:43:18 2026 [/code]

Herra Sebaot

OH! I learned a thing! Renaming old version was NOT smart! Deleting old files solved the problem! A suggestion: Instruct users to REPLACE the files, not just to copy them to folder nnn. (I tend to save old versions for “security”) But I sure like the game! An additional idea, if you please… There seems to be pretty little variation in ship battles. Asteroids and ships are every time on same spot. Would it be possible to locate them randomly? This would make battles more interesting.

y.v.

yes, it is always a very good idea to install every new release in a completely new folder. Your save games won't be affected by that because they are stored in a separate central location. You can safely delete the folder with the old version.

y.v.

I also wrote the warning in the reference document and walk-through that it always must be installed in a fresh folder. But you know what they say about walk-through documents. If you want to make sure a secret is never revealed, you write it in the walk-through because no one ever reads it. :)

DeedlitdieElfe

Another Bug... starting a new game going to the Captain cabin to retrieve the commandbangle... all good. Leaving the Captains Cabin starts the news announcement about mining and nothing happens... trying to enter the hallway infront of the bridge again, the dialogue repeats, this time throwing me into the storage area, going up to the hallway infront of the brisge again repeats this into an endless loop. And yeah I installed the patches

y.v.

this sounds like a major corruption issue. It would have shown up in any test. I will do a quick replay of the early content but I am almost certain this is related to an installation issue. No fresh folder? Installation of a outdated patch not fitting to the version which messes up return points? If you have access to Discord, I would like to see that save game for analysis if you know where to locate it.

DeedlitdieElfe

I think I figured it out, I used the patches from last download link in the thread, which was 2.30... makes sense it fucked the game up, my bad

asdman64

i'm loving this game and all the little extra bits added in V240 are terrific.

y.v.

I have thought about your report it and I think I know the root cause. Even when installing a patch, it is better to do that for a save game, which is at the nightly screen and not somewhere deep down in the call hierarchy. The patch modified one procedural call and if you were the wrong place your return jumps would go all over the place as you reported. TLDR install the patch and resume from a safe spot save game