tickle_me_jesus

Where is that other thread where people said it didn't work still? Anyway, I'm guessing you need some patience before we get some confirmation about the tent/vehicle saving fix. People need to update the servers, clients need to update their game and servers need te be restarted multiple times before anything certain can be said i would think.

lol....

No, the hive is currently on version 0.7.3 and maybe because of the rolling DayZ update 1.7.2.6, hive version 0.7.4 is released. I think you might be confused by future DayZ update 1.7.3? Which is another thing.

-nevermind- Found the update you are talking about http://dayzmod.com/forum/index.php?/topic/87541-pending-update-build-1726

Support ticket #435080. You did answer it indeed :)

Good news...my server has had the status 'starting' all day and is now on 'error'.

I had this happen one time also (another host though) and never got an answer of them how it exactly happen. In first instance they pretty much accused me of changing it myself...just lol, as one can hardly change anything at all on slotted servers let alone such things as available slots. Long story short; submit a support ticket they will fix it soon enough. p.s. If you however do get an answer from your host how these changes came about I would like to know, out of curiosity.

Yeah, wish I had done that. Seriously have no clue what th instanceID was and can't find it anywhere in the config files. About the BEC thing; I had setup the scheduler.xml to announce the regular restarts. It didn't save though, so I am also a bit in the dark about this one. I assumed you have to go to your 'configuration files'. After you installed the BEC it will show you some new configurable files What is and what is not needed to setup isn't clear for me, but I used http://ibattle.org/i...-and-configure/ as reference to setup the scheduler.xml. I don't know if you need to configure any of the other files to make it actually work, bu I think you will need to setup the config.txt (BEC config) also. Keep in touch and let me know if you figure it out!~

You might add to that the following basic issues which are not being resolved: - 24/7 availability of the ACP (the server control panel) - scheduled restarts actually being completed. It just starts skipping scheduled restarts, no matter how many times you set them up - random shut down of your server. It will just stop your server, no reason given and when asking for support about the issue they just imply you did it yourself

I have the exact same thing; The instance id got reset in the cfg file and now just states 'instance id'?!

Lol...Well, you know I'm shutting down the current NL101 (difference of opinion with Vilayer hosting). But your more then welcome on my new server DE 2634 (location ID change pending)

^^ I do that every time and so far it works. Sometimes it won't work the first time, but it still is the only thing that actually helps at all.

Unbelievable. The community finds a temporary fix for a problem the DEVteam have a) kept silent on for over almost a month b) shown zero intentions on supplying a hotfix Yet, they are quick on their feet when it comes to telling something is not allowed. As if the supplied fix did anyhing 'gamebraking'; exchanging some files from 1.7.2.4. onto 1.7.2.5.

Ok, I ordered and paid for a server this afternoon. Within 6 hours of applying the server is running. So far top service. The TCAdmin works nicely and is comparable with the control panels used by other companies. If you know your way around them it's really easy to set up you server the way you like it. There are two small things that might need attention though: - The remoteexec.txt and createvehicle.txt are not implemented and therefore don't create the needed logs to administrate your server efficiently against scripters. Since the server just went online i am not sure if both files will be added automatically. For reference about these usefull files see http://dayzmod.com/f...cheat-features/ http://code.google.c...munity-banlist/ - I haven't got around setting up the automated restarts, so i don't know if that works. There is a TAB in the TCAdmin for scheduling restarts, but I couldn't open it. Will update if anything comes up that might be usefull for others or the above needs updating

That would be most excellent :) My server ends on 6th of september, and I'm not planning on staying with my current server host. EDIT: Just ordered one through your website.

Any estimate when new servers in Europe (Frankfurt) will be available again?

Don't bother asking...they will give you some BS answer implying you did / changed something which made the server stop. I have like 5 answers from them in my support stating exactly that. I'm not sure how stubborn they are but they will sell you any bs before admitting they have an actual problem on their end. Sick of it and totaly done with Vilayer. There are enough other providers out there.

Sigh...ACP not reachable (again) and server was stopped (again) without any reason. EDIT: lol...put in a ticket about the issue. Their answer: "This is a known issue". No sh*t Sherlock! You would think the known issues would get fixed, eventually.

Don't have enough knowledge to make a statement like that. Half the problems? Really? Hmm, well each and every single problem I am having does not have to do with me changing stuff. Random shutdowns of the server? > Vilayer doesn't even investigate it and just assumes I stopped it myself or locked the server. Right...Hadn't logged in to the ACP the whole day because I was at work, yet the server gets stopped Problems reaching the ACP? Yeah, we all been there. That had also nothing to do with us clients and we were not causing this, were we? Continuous skipping of scheduled restarts? Have set up the scheduled restarts a dozen times, yet the server fails to restart sooner or later and starts skipping restarts till the point it restarts one time a day (if I'm lucky) Long story short; Vilayer was a fine host the first month (july), but since august it has gone downhill. No improvement sofar. Johnny and Lee might be really nice guys, but as far as I see it this isn't about exchanging pleasantries. This is a customer - provider relationship. I pay for a service and they need to provide, plain and simple. No BS about alpha stage, cause that argument doesn't hold for any company that charges money for their product.

Ok, I'm seriously done with being nice. Anyone else having problems with their server getting randomly stopped? I have been having this problem this whole week after the so called 'security patch' (BS anyways, as both createvehicle.txt and remeoteexec.txt were allready logging before this) my server gets stopped. Contacted Vilayer through their ticket system and always get some dicktwat answer instead they actualy fixing the issue. So f'ing fed up with this.

I don't know what your problem is, but did you perhaps recently installed any Arma 2 DLC (BAF or PMC)?

No need to restart your server. Just check if the GUID was added to the ban list. If it was he will not be able to log in again on your server. Again: if he is playing on the server while you add his GUID to the list he will be able to stay on the server. You will need to kick him of the server first, after that he won't be allowed in again. Oh, and you are adding to the bans.txt, this is another file than ban.txt You are wrong; GUID is generated of your CD-KEY. If you change your CD-KEY (e.g. buy a new copy of Arma OA) you will receive a new GUID and will no longer be (global) banned.

Easiest would be to use a third party tool like Arma 2 RCon GUI or BeRCon (google for it) Once logged through your RCon tool to your server you can add bans > commands > Add Ban >Copy/paste GUID and select default option cheating/hacking Because you ban someone on their GUID it doesn't matter if they change their ingame profile/ name...still banned. Only using another game key will get them past this ban. Once you have done this, go into your RCon tool to the tab bans..wait for it to load and scroll all the way down. You should see the banned GUID you just added. p.s. If a player is on playing on your server while you add his GUID to the banlist, it won't work most of the time. You need to kick said player first of your server.

shit...having to go through scripts.log is tedious, mine is 1.3 Gb :)

I'm guessing your with Vilayer also (LU id). It's probably nothing you did. Just Vilayer having some strange issues today. Today my server was stopped and changed to 64 slots (instead of the default 40) and the name changed to eu124 (my server is NL101). Vilayer then sent me an e-mail asking me to explain what happened. WTF? As if I could change that. I can't even change the Rcon password in the BEservercfg and make the change actually stick, let alone change the amount of available slots on a machine.