snipertyler

Yup.. password was unique to this site. No issues there (for me) This sounds like they got access on 3rd Aug and just started logging things since then. In any case (from perspective of someone running a web-server) I'm curious how you managed to detect them? (Might be able to share some advice on securing)

md5 checksums! Excellent. I'm not super aware of how lua & loaded mods work, but it would be a good idea to ensure that anything dragged into "Includes w/e" is also checked. I prefer sha1 over md5 but it's much better then nothing. .bat is for Windows (dos batch file) .sh is for Linux Bash scripts. The projectzomboid64.sh works fine - although the very old erroring command continues.. INSTDIR="`dirname $0`"./projectzomboid ; cd "${INSTDIR}" ; INSTDIR="`pwd`"resulting with ... line 10: cd: ~/.steam/steam/SteamApps/common/ProjectZomboid/projectzomboid./projectzomboid: No such file or directory changing it to this fixes the problem. INSTDIR="`dirname $0`"

I see what you mean by copying and pasting complex strings of text. Gotta start somewhere. As for updating it... I don't know what the "Default install folder" is, but why not make it a function and place in .bashrc or .bash_aliases? Most people are using Ubuntu/Debian I think Assuming the user is steam and the directory to install in is ~/Zomboid/PZServer and the onlinetest beta installed to .local/share/Steam/SteamApps/common/ProjectZomboid/pzserver for the below command. (Fyi, reads are deleted when exiting a subproccess, --> a=2;(a=5); echo $a -- Cool little trick I learned awhile back.) updatepz() { (killall projectzomboid-dedi-server.sh; read -p "Enter Steam Username " un && read -sp "Enter Steam Password " pass && ~/Zomboid/PZServer/steamcmd.sh +login $un $pass +force_install_dir ~/Zomboid/PZServer "+app_update 108600 -beta onlinetest" validate +exit); ~/.local/share/Steam/SteamApps/common/ProjectZomboid/pzserver/projectzomboid-dedi-server.sh; }There's a lot of fragmentation right now. The guide shows steamcmd going into it's own folder, Zomboid/db in it's own (still not .Zomboid), then a entire other folder for the game files. In theory though, running or crontabing the above command would kill the existing server, update it and restart it.

May I add some tidbits about the guide? First Running the dedicated server while putting in your password will lodge your password into the history (type history in the terminal to see previous commands) This can be a security problem, even if you consider yourself the only one with access, it would take only a moment to do history > log and grab it. To prevent that, type in unset HISTFILE previous to that command. It will disable logging temporarily for that session. Second- Instead of running screen, then changing directory to the .sh, then running ./projectzomboid-dedi-server.sh why not run screen -dmS PZServer /home/steam/Steam/SteamApps/common/ProjectZomboid/projectzomboid-dedi-server.shAnd have everything done at once? -dm disconnects the screen automatically and -S gives it a name Type screen -x PZServer to check in on it. Thirdly- why not do: The -p arguement automatically creates directories if they don't exist and you don't need to be in the directory to create it. _____ Sorry if I seem nitpicking, but this will compress the instructions and up security a bit to those unfamiliar to linux

This isn't entirely correct, you'll get a "error.txt" file at the end, but it'll be blank. When you want the errors from a program, you need to place the 2>file after the command ie: foo 2>error would put out a file "error" saying "No command 'foo' found, did you mean:, etc" 1 on the other hand, puts out normal output echo hello 1>normal (Little extra info, &>file means both error & normal) Putting a bash script like this would not work (as you want it): echo hello foo hello 2>error Try this: echo hello foo hello 2>error However, this won't do the whole file, just the failed foo command. To do the whole file, you can go to the projectzomoid.sh directory in the terminal and run ./projectzomoid.sh 2>error.log Or, a little workaround, put the entire file into a subprocess and then add a 2>error at the end. ( echo hello foo hello ) 2>error But the easiest way (for me) is to simply open a terminal, go to the projectzomboid folder, and attempt to run it there. Any errors will be output to the terminal and you can copy and paste from there. ============== Fyi, I would reccomend backing up any files you might change. copy and paste would be fine. The pz folder for steam is located here: ~/.local/share/Steam/SteamApps/common/ProjectZomboid .sh is *similar* to .exe but more similar to .bat files To start a terminal, hit the "windows" key and type terminal, or hit <ctrl>+<alt>+<t> (for ubuntu)

I don't know how to fix the null point exception, but this error: projectzomboid.sh: 21: projectzomboid.sh: [[: not foundcan be fixed by replacing (in projectzomboid.sh) [[ ! -d "${GAMEDIR}" ]] && mkdir -m 0755 "${GAMEDIR}"with if [ ! -d "${GAMEDIR}" ]; then mkdir -m 0755 "${GAMEDIR}"; fiThe 1st one isn't as posix as the second. You can test this (if it doesn't occur to you) by running 'sh projectzomboid.sh' versus 'bash projectzomboid.sh'

I figured out how to run pz in the latest steam release for Linux 64bit using Mint 15, I posted my instructions below. I'm not sure of the version, but in the bottom right I see '17 (0014)' _____________________________ In the latest steam release, pz for linux does not boot. I ran my lwjgl command but there was still no result. I ran the program directly in terminal and got this: ./projectzomboid.sh: line 11: cd: ../projectzomboid: No such file or directoryError: Could not find or load main class zombie.gameStates.MainScreenStateNow, the first error has occurred in the past and didn't affect the game. However, it does now, so we need to fix it. I don't know if you recognize this though, but .. is a way of saying in bash (linux) to go down one directory. For example, at ~/Music/indie if you ran cd ../rock you would go from ~/Music/indie --> ~/Music --> ~/Music/rock Relating to our script, doing the exact opposite of what our developers want! So how to fix? Edit the file projectzomboid.sh at ~/.local/share/Steam/SteamApps/common/ProjectZomboid In the line that contains this (INSTDIR one): GAMEDIR="${HOME}/.project_zomboid_2.9.9.17"LOGFILE="${GAMEDIR}/${SCRIPT}.log"--> INSTDIR="`dirname $0`"./projectzomboid ; cd "${INSTDIR}" ; INSTDIR="`pwd`"Delete the last line and add this: cd `dirname $0`if [ ! -d projectzomboid ]; then INSTDIR=`pwd` else INSTDIR="$(cd "projectzomboid"; pwd)"; cd $INSTDIRfiso that it looks like this: SCRIPT="`basename $0`"GAMEDIR="${HOME}/.project_zomboid_2.9.9.17"LOGFILE="${GAMEDIR}/${SCRIPT}.log"cd `dirname $0`if [ ! -d projectzomboid ]; then INSTDIR=`pwd` else INSTDIR="$(cd "projectzomboid"; pwd)"; cd $INSTDIRfi[[ ! -d "${GAMEDIR}" ]] && mkdir -m 0755 "${GAMEDIR}"JARPATH=".:lwjgl.jar:lwjgl_util.jar:jinput.jar"If you're wondering why do a if test, you can do the same thing in the projectzomboid.sh file inside ProjectZomboid/projectzomboid/ and won't screw up the script (as the orginal code did) Might be helpful to dev's...

For me java has never been simple on linux.. I downloaded and extracted the "official" 32bit java edition Now how to get steam to run pz using this edition? I listed what I tried below... no success. I modified the projectzomboid.sh file and prepended alias java="/usr/share/java/jre1.7.0_25/bin/java"$ java -version java version "1.7.0_25" Java SE Runtime Environment (build 1.7.0_25-b15) Java HotSpot Server VM (build 23.25-b01, mixed mode)

So for me pz doesn't work with 64bit linux mint through the steam download. I get a immediate crash when loading. Same with compatibility mode. I ran the projectzomboid.sh in ~/.local/share/Steam/SteamApps/common/ProjectZomboid to grab any terminal output. Here's what I got: $ bash projectzomboid.sh net.puppygames.steam.SteamException: Can't load native libraries at net.puppygames.steam.SteamAPI.create(SteamAPI.java:76) at net.puppygames.steam.Steam.create(Steam.java:40) at net.puppygames.steam.Steam.init(Steam.java:64) at zombie.core.Core.init(Core.java:1378) at zombie.GameWindow.init(GameWindow.java:1341) at zombie.GameWindow.maina(GameWindow.java:887) at zombie.gameStates.MainScreenState.main(MainScreenState.java:98)AL lib: (EE) alc_cleanup: 1 device not closedthis doesn't *look* similar to the xinitthreads problems I'll try installing 32bit java as recommended in the morning and see if that fixes it..

I used too. It sucked though because you had to do so much to prevent it from "calling home." and worry about anti-piracy listening in on torrents, unreliable installs, high potential of infection; hell most crackers were identified as viruses... to be honest though, I was more into the modifying the files then stealing. Ever use Artmoney on Unreal Tournament 2000? So much fun with the rocket launcher Eventually I found linux though and it pretty much fulfilled everything I ever needed. Everything is a lot more fluid when I want to change... pretty much anything. If I want something, I create it instead of buying it (or pirate)

I got the common Main exception error and doing this got me to here which output this when I moved the mouse over the screen: AL lib: ReleaseALC: 1 device not closed Doing it again got me this: and a different message the next time.. The bolded part sounds like the posts above ^^ Edit: This isn't important, and I don't know if anyone has noticed this, but in the projectzomboid.sh file, the line containing: INSTDIR="`dirname $0`" ; cd "${INSTDIR}" ; INSTDIR="`pwd`" looks like a long way of just doing this: INSTDIR=$(pwd) I run the Amd64 version Kernel: 3.8.0-19-generic x86_64 (64 bit, gcc: 4.7.3) ; Linux Mint 15 Olivia (derived from Ubuntu) Graphics: Card: Intel 3rd Gen Core processor Graphics Controller Java version "1.7.0_25" OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.13.04.2)

I have the invisible wall problem. It also affects zombies as well, who can't pathfind to me at all as you can see here

I've been building and reading commands from commandlinefu and it blew past me to write a local script lol. I took your script and modified it a little bit, I hope that's ok 1. I re-directed the .zip file back to ~/Downloads and removed the "rm". Now you can run the script in multiple builds without needing to re-download constantly, especially with the frequent forum builds. 2. I added a #!/bin/bash at the top to identify it as a bash script. Thank you for using the -O arguement. I did not know that existed and was ticking me off. I normally use aria2c (aria2) and it doesn't have that weird naming problem.. I wouldn't recomend using it as a alias as once it's in place, it's a one time usage. I would suggest a function. But that gets back to using a variable for the most recently extracted pz folder. Also.. After creating a script, you'll need to run chmod +x pz-fix to let it run as a script

aria2 permits designating the directory. However, you're right, it would be a better idea to have a more posix style command. Edit: I modified the post to use wget instead of aria2c

Tested on 64bit & 32bit builds. So the Linux versions, Debs and Tarballs have this on-going problem of not being able to even start. The stand-alone seems to work. However, the Desura, Steam and forum unstable builds have this problem. After a fun time of trial and error, I identified the problem file, liblwjgl.so (and liblwjgl64.so for 64 bit) They need to be replaced by the new stable build of LWJGL. Download the zip and extract the appropriate file to the projectzomboid folder. It is located in lwjgl-2.9.0.zip/lwjgl-2.9.0/native/linux/liblwjgl.so (and liblwjgl64.so for 64bit) For now, this should fix the problem. I developed a terminal command to do this all in one step. Change the pzfldr variable to your extracted projectzomboid folder (for the forum edition) Run the command, then enter A<Enter> when indicated for replacing the file. Forum Edition: This will work when pz was extracted to a place where you have write permissions. (Try this one first as it lets you easily specify where your pz folder is) pzfldr="/PATH/TO/projectzomboid/"; if [ ! -f ~/Downloads/lwjgl.zip ]; then (cd ~/Downloads; wget 'http://sourceforge.net/projects/java-game-lib/files/latest/download?source=files' -qO lwjgl.zip); fi && (cd "$pzfldr" && unzip -j ~/Downloads/lwjgl.zip lwjgl-2.9.0/native/linux/liblwjgl64.so lwjgl-2.9.0/native/linux/liblwjgl.so)If you installed it using Steam if [ ! -f ~/Downloads/lwjgl.zip ]; then (cd ~/Downloads; wget 'http://sourceforge.net/projects/java-game-lib/files/latest/download?source=files' -qO lwjgl.zip); fi && (cd ~/.local/share/Steam/SteamApps/common/ProjectZomboid/projectzomboid/ && unzip -j "/home/$USER/Downloads/lwjgl.zip" lwjgl-2.9.0/native/linux/liblwjgl64.so lwjgl-2.9.0/native/linux/liblwjgl.so)If you installed it using a deb file (which installs to /opt/projectzomboid/ and requires root) if [ ! -f ~/Downloads/lwjgl.zip ]; then (cd ~/Downloads; wget 'http://sourceforge.net/projects/java-game-lib/files/latest/download?source=files' -qO lwjgl.zip); fi && (cd /opt/projectzomboid/ && sudo unzip -j "/home/$USER/Downloads/lwjgl.zip" lwjgl-2.9.0/native/linux/liblwjgl64.so lwjgl-2.9.0/native/linux/liblwjgl.so)Thank you tazyload for showing me where to find the LWJGL build! CareBearCorpse also made a script that you can simply run as needed inside the projectzomboid folder. I posted this originally here but figured support might be a better place to put this..

Are you on 32bit or 64bit? I'm curious because if you are on 32 bit, does the command I posted here fix the problem? It just copies the liblwjgl.so file (and liblwjgl64.so) so I'm hoping it's a one step fix for each version.

Hey Dev's! ___________ EDIT: Posted fix to linux versions not working

Hey Dev's! Looks like the tarball is not working still. EDIT: Posted fix here Even if nothing changes, that is fine! This is a great game guys! Keep it up

So the Linux AMD64 .deb does not work Here is the LOG and the stdoutput "Exception in thread "main" java.lang.NoSuchMethodError: Method org.lwjgl.openal.ALC10.nalcGetString(JI)Ljava/lang/String; name or signature does not match" It looks like a case problem. However, the stand-alone version stable works. I am so going to make this work.