Search results

If you have vehicles in your objects_data table, look back at the first 10 or so pages for a posted fix.

We use Gotcha Antihacks. But the hack portion isn't that good. It does have the ability to kick people having restricted weapons in their inventory. But not all weapons are listed, so hopefully it covers the majority. We have had 6 people kicked in the past 2 weeks with restricted weapons.

Tried that fix and we still see the occasional loss of house inventory.

That's ok - I forbid you to use them. Take that. lol

Instead of just posting for the 1.7.5 server files, why don't you read the last 2 pages for yourself and get caught up with the discussion.

I added a new group to sec b in the industrial, and made it g18g. My only problem seems to be that I don't see the kill messages when killed by them. Any idea where and what controls the death messaging?

Here's was the suggested fix. Going to add it to ours and see how it goes.

Did you blank out the passwords in the second crash report? Or is it bugged. Wondering since the password appears in the first report.

No expert at it, but would you just copy the g14g section and paste below renaming as maybe g18g, change the spawn locations and then call the spawn function at the bottom. Gonna play around with it.

Would that not be in the @dayorigins? Or is it in the server files?

If you look in your log, you should see file not found. It's not packing the .pbo with the prefix. I tried it again with 2 tools with prefix set and it's still not setting it correctly.

I am not sure what's going on. I have tried 3 different tools and none seem to work.

Try downloading it again. I packed it with another tool and added the prefix. Updated the tools and the readme for instructions for adding the prefix.

Yea - I guessed at the prefix file since when I unpack it, I am not getting one. Is the one that is already packed not working?

I have a template here: https://github.com/MajorPainage/OriginsStart or At the end of your .bat, add the line "pause" without the quotes. This will keep your console open so you can read what's happening, and you just have to hit a key to close it.

I think I see the issue. Have to remove the time sync from the server_cleanup.fsm. Will do some testing tomorrow.

Here's another thread explaining it all using more variables. http://opendayz.net/threads/accelerated-time.8717/page-3

I don't understand the instructions fully, but I think you go with 12hr day and 12 hr night. 12hr / 4hr = 3 multiplier. 12hr / 2hr = 6 multiplier. You can read the instructions here and see if it makes sense to you: http://forums.bistudio.com/showthread.php?137061-MP-Fast-time-FSM-JIP-Compatible

Try: //Adjusts for 4hr day/night [3,false,true,6] execFSM "core_time.fsm";

If they are unbanned you can spawn them. Check in your logs and it will show if they are banned.