Jump to content

jdragun

Members
  • Posts

    20
  • Joined

Posts posted by jdragun

  1. 3 hours ago, Subquake said:

    Glad you think that way, yes I work alone, besides a few instances where I asked some advice from sphereii and Khaine as well as translations were offered by fans of the mod, but the code, content, user interface, web etc - that's all me for better or worse :)

     

    Though I am also very grateful for the growing community of Undead Legacy fans and their feedback and stories of playing the mod, feedback is very important for me to judge on what aspects should and could be improved in future iterations of Undead Legacy :)

    Just want to say thank you.  I have been running this mod since you started it.  My server always has people that love it.  Your hard work and dedication do not go unnoticed.  Ignore any @%$#s that don't understand the time it takes to do this and that you have a life other than this.  Looking forward to you "Fixing" the issues with vanilla A20 when it comes out on stable branch.  I just went to 20ExP, and I forgot how to play vanilla!  This is the best mod out there!  Thnak you again.

    • Like 1
  2. Is there a way to automate updating this mod?  I am running a linux server with LSGM, I've tried to add it to my script when I check for updates from the game server, but nothing I try works.

  3. Thanks, I think I have it narrowed down to a .net issue. Went to update .net just to see whats up and that will not update, now it seems there is a can of worms I opened here, all my updates are fubar(d). Doing some rebuilding here. I am sure it's not your coding, but my .net. Just for the record, I7 2.8, 16 Gig Ram SSD HDD Windows 7 x64 ultimate, Nvidia 650ti, Bit Defender Free, turned all off and still just see a flash of a screen, looks like an error screen, but I cannot pause it o see.....

  4. OK. I don't get it.

     

    I modified startserver.sh to

    #if [ "$(uname -m)" == "x86_64" ]; then    ./7DaysToDieServer.x86_64 -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt -quit -batchmode -nographics -dedicated $PARAMS
    #else
    #    ./7DaysToDieServer.x86 -logfile 7DaysToDieServer_Data/output_log__`date +%Y-%m-%d__%H-%M-%S`.txt -quit -batchmode -nographics -dedicated $PARAMS
    fi

    And yet the log is still showing 32-bit.

     

    Going to have to start a fresh box up and test on it I guess.

     

    Edit: New box, fresh install, and still I get...

    2016-02-22T21:19:41 0.087 INF Version: Alpha 13.8 (b7) Compatibility Version: Alpha 13.8, Build: Linux 32 Bit

    2016-02-22T21:19:41 0.087 INF System information:

    2016-02-22T21:19:41 0.129 INF OS: Linux 4.2 Ubuntu 15.10 64bit

    >.<

     

    I am also running the dedi mods and the start.sh calls the 32 bit version. Is there a reason for that? I am running Ubuntu Server 64, and don't know if I should just edit the start.sh to call the 64 bit version or not. Will that effect anything? What is the major diffrence between the 32 and 64 versions other than mem use?

     

    Do you still have to edit the startdedicated.sh in the /home/sdtd/engine/ dir?

×
×
  • Create New...