Obsidian Conflict Forums

I just noticed 1.34, it's been so long
Updating that lovely 3dslice.net server to this right now.
Keep up the good work

EDIT: having a problem with the installer
Keep getting something about An error occured while tryign to rename a file in the destination directory:
MoveFile failede code 183
Cannot create a file when that file already exists.
I'm using the patcher if that matters.

I got that a couple of times too

I got it more than 10 times lol.

Anyways, I love the fix on the CSS weapons. Thanks for the fix.

JigglyWiggly wrote:I just noticed 1.34, it's been so long
Updating that lovely 3dslice.net server to this right now.
Keep up the good work

EDIT: having a problem with the installer
Keep getting something about An error occured while tryign to rename a file in the destination directory:
MoveFile failede code 183
Cannot create a file when that file already exists.
I'm using the patcher if that matters.

I think thats a file in use error, was your server running an active connection when you where updating it? For others, you may have to close Seam to update it and and make sure your not using the mod while patching (check that all processes are closed)

You get that error if you install the SMOD components. Not sure why but it says a file is in use for me too and I don't have SMOD installed.

Ny wrote:

JigglyWiggly wrote:I just noticed 1.34, it's been so long
Updating that lovely 3dslice.net server to this right now.
Keep up the good work

EDIT: having a problem with the installer
Keep getting something about An error occured while tryign to rename a file in the destination directory:
MoveFile failede code 183
Cannot create a file when that file already exists.
I'm using the patcher if that matters.

I think thats a file in use error, was your server running an active connection when you where updating it? For others, you may have to close Seam to update it and and make sure your not using the mod while patching (check that all processes are closed)

It is a file in use error, but server is off and I even tried applying the patch to a blank directory, same error.

it's not SMod that's something else, call it SM or SourceMod...

Yeah my steam was also off when I did it, yet I still got it.

http://www.obsidianconflict.de/forums/v ... 2891#40433

only use the sourcemod thing if you patch a server NOT A CLIENT

So anyone have a solution?

keep pressing irgnore and do as i said in the other thread

I already did that, but like for other people this is probably inconvenient. Why don't you guys just repair the archive? I mean it makes no sense to host something functional but with errors right?

1.34! Thats the second mayjor release in a row now I've missed...