1. This forum is ARCHIVED! Visit the new Cloud Sixteen forums, codename Eden, at https://eden.cloudsixteen.com. These forums will remain archived for a few months before being closed down, so try to encourage plugin developers to begin moving their content across to the new forums.
Dismiss Notice
Hi Guest, you need a Steam account to register and post on these forums. Login with Steam at the top of the forums to get started!
Dismiss Notice
Hi Guest, do you want to buy HL2RP or another Clockwork schema? Visit the Cloud Sixteen Store to get started!

HL2RP Crash server for 1 player. [FIXED]

Discussion in 'Discussion' started by Desqer, Jul 5, 2016.

  1. One player joins the server and the server crashes immediately. When connecting other players. It's okay. No error does not write to the console.
     
  2. Songbird

    Songbird ❤️ Staff Member Moderator Legend

  3. Bump
     
  4. There's really not much to go off of here. Have you tried enabling the -condebug and looking through the console.log? You're pretty much guaranteed to find any error that isn't written in the console.
     
  5. I'll try. Thank you for attention.
     
  6. Squirrels Mcgee

    Squirrels Mcgee fallout 4 = "power armour hoarding sim"

    I would assume its client side if its only persistent for that specific player.
     
  7. On the client all right when the player comes to other hl2rp server then all is well. This is a problem in the server. Those who have any ideas why this is happening?
     
    Last edited: Jul 7, 2016
  8. Nobody will be able to help?
     
  9. If it's only one person then it's probably client side, just as Squirrels said. Get them to verify the integrity of their game cache, and delete any addons that could possibly conflict with the server. If it's only occurring with one person then it's something with your specific server that's causing him to bug out. Maybe the map, maybe the gamemode, who knows.
     
  10. The problem was solved by removing clientregistry.blob.
    This file crashed CW and Client.
     
  11. Resolved: The problem was in the files: garry's mod/lua/clockwork.lua. We have deleted the file, and then load a blank file.
     

Previous Readers (Total: 0)