Author Topic: Script_Player_Persistence  (Read 1854 times)

i found out today that this addon was causing my game to crash on the last stage of the loading screen and thought i better post it here to warn others it will show itself by making the screen grow black untill there is only a small round center of the screen visible, this problem can be solved by disabling it in the list of addons, hope this helps somebody.

Give us a console.log of it happening.

iv'e attached the console log hope this helps someone

iv'e attached the console log hope this helps someone
Blockland didn't crash. You exited out of out.

it loads the gamemode as normal, but when it's finished, instead of loading up the terrain you get this weird glitch where the screen goes black on all sides but leaves a small circle view of the loading screen, i tried to take a screenshot of it but it comes out black, for some reason you can still open the pause menu and even change the gamemode and leave the game, which is what i did becouse you wanted to see the console log

iv'e attached the console log hope this helps someone
So this happened when you ran the game with only Player_Persistence enabled? Don't see how this problem could occur without an add-on conflict of some sorts.

I don't know. Try deleting Script_Player_Persistence and Support_Player_Persistence. Then the launcher will re-create the files. Then try it.

indeed -jetz, and what puzzles me is it still seems to load the support version even though i made sure only the script version was enabled. but support_player_persistence works fine and i don't seem to need the script version.

indeed -jetz, and what puzzles me is it still seems to load the support version even though i made sure only the script version was enabled. but support_player_persistence works fine and i don't seem to need the script version.
That would be because Support_Player_Persistence does nothing on its own, and Script_Player_Persistence requires it to run. Would you mind opening the console before you start the server, typing trace(1); and then proceeding to start it? Feel free to quit after encountering the bug, then post the log. I just can't come up with any reason this would happen. That log shows exactly one add-on running on the server.

ok here it is

Quote
==>trace1
Syntax error in input.
eval error >> trace1
BackTrace: ->ConsoleEntry::eval
Missing the parentheses and semicolon. You'll know it's worked if you either see "Console trace is ON," or don't because the console quickly gets flooded with tons of new lines because the game is telling it everything that happens. It'd probably also be easier to spot the error with just the player persistence add-on running rather than  the large selection shown in this log.

On an unrelated note, that TF2 butterfly knife you have needs Emote_Critical to work. Might want to pull it out of an RTB archive.

third times the charm? lol
and thanks for telling me about the knife

Okay I got no clue why the game wouldn't properly set your control object when you spawn, or more specifically why it'd be dependent on an add-on that doesn't seem to do anything like that. I ran the game with just that add-on enabled and it worked fine, and my console log's spawn process is identical to yours. Either I'm missing something here or there's a bug in the base game that I can't check. It's easy enough to simply not run the mod, since servers rarely have a use for it, but if you want to, you can probably fix it by hitting F7 when you're supposed to spawn.

i did the f7 thing and it let me play, then i disconected and joined again and it crashed and shut the game down, unfortunately i was unable to re-create this as it isn't having any problems now! thanks for the help

Badspot

  • Administrator
From your Blockland folder, go to config->sever->persistence
Find the files 100211.txt and 999999.txt and post them here.