Welcome to The Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies and more


riddlogic

Members
  • Posts

    32
  • Joined

  • Last visited

  1. My issues may be related to this too. Sometime around Monday my server started to seemingly restart itself every few minutes. I'm not sure that it was a true restart, but it would kick everyone and all my admin tools (dart, tsw) for about a minute and then everything would come back normally. Unfortunately this would continue to occur every 5-10 minutes making my server completely unplayable. I've also submitted a ticket but with the very slow response times and unhelpful at that, I've still been offline since Monday morning. A day is understandable, 2 days is unfortunate, over 3 days now is... well, incredibly frustrating for me and my players.
  2. I followed this thread to get autorefuel working on my server. http://opendayz.net/index.php?threads/d ... ions.7056/ If you actually read through the thread, there are 2 different methods used. The second method uses a couple scripts and is much, much easier to implement. I'd recommend going with that as it's just adding some script actions and not actually modifying your mission code. It also makes autorefuel work on all fuel-based objects (gas stations, tanks, etc) instead of the coordinates based approach in the first one. As for the rest of what you're trying to do, the pbo used in the above fueling scripts is probably the pbo you would use for the rest of it.
  3. The DayZ guys acknowledged this issue with the humanity system (and changing skins in general) on the forums. Hopefully fixed in the next update. http://dayzmod.com/forum/index.php?/top ... e-help-me/
  4. When my server reaches over 30 people I also get reports of lots of "red chains" and desync/lag. I don't think these servers are up to par for 40 people running lag-free.
  5. Sorry you're still getting this issue. Updating all of my filters from the link we provided before fixed my issue right away. A server restart is required obviously. https://code.google.com/p/dayz-communit ... e/filters/
  6. TSW is not a replacement for BE. And I think we're all getting that "failed to connect" message. Not sure what's up with that.
  7. Does every post you make have to be so full of snark? Stop the hate bro.
  8. That's exactly the issue, Sabar. A varchar column of length 0 can't store the amount of data being entered, even if it just an empty array. Mine are set at 25 though I guess with what is actually being put in the rows, a value of 2 would work. Though I think varchar stores 4 bytes regardless... anyway. You can't leave them 0. Bjoern, you didn't do anything stupid. Sounds like you've got everything working correctly.
  9. The first thing I'd do is download my HiveExt.log and see if there are any errors reported in it. Database-related errors about saving new tents to the db will show in there. If you see some post them. When I was having issues with new tents being added to my database it was because I hadn't discovered that Hitpoints needed to be a varchar yet.
  10. Glad you got it all working! Not trying to sound like a dick, but everything you described was exactly as discussed here. Instance deployable had to be wiped for all of us. =P
  11. Yes, only Hitpoints need to be varchar. Sorry if it was confusing, it took me a long time to figure all that out and I was groggy by the end of it. =P Hopefully you're doing it through the Structure tab in phpmyadmin, that's the easiest. More info: Vehicles will work if Hitpoints is an Int, but deployables won't save. Hitpoints has to be a varchar for things like tents to save.
  12. I installed everything normally via the mod manager. Then I copied all the scripts from that link to: /Bliss/BattlEye/
  13. While admining a server is certainly not the easiest thing to do, it's not rocket science either. There is a learning curve but there are plenty of help resources out there if you aren't afraid to Google. Don't mind the snark of some "superior admins".
  14. That's exactly what I did and I posted the solution. So thanks for... repeating it?
  15. Here's my post from a thread before this. Using these updated filter files fixed this issue for me.