Forums Announcement
Read-Only Mode for Announcements & Changelogs
Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.
For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.
Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!
Stay safe out there,
Your DayZ Team
-
Content Count
879 -
Joined
-
Last visited
Everything posted by drgullen
-
If this is truly the goal, why not just get rid of the hive system altogether? Those of us who are not base raiders/destroyers or loot dupers or any other kind of cheater are suffering from this solution -- I should not have to be placed somewhere back on the coast if I have been "playing the game properly" and have made it all the way up to the northern part of the map, for example. You've solved the hopping problem by creating a new problem for those genuinely not hopping. I'm sorry, this is not a good solution.
-
Sure it's possible -- there's miles and miles of beach you can explore! 😋 Seriously though, I agree 100% -- I hate the solution they've implemented for server hopping. They need to go back to the drawing board with this one.
-
Can you get the server up and running with the default init.c file? I would try that -- if that works, it means you have some mistake in your init.c perhaps.
-
I think what they mean is if you have a custom types.xml file for example where you've reduced the loot a lot let's say, you would place that file in your mission folder, so that as patches come out that update the default types.xml file, your customizations won't get overridden. That's how I read it anyway -- haven't tested it myself. You're right though, it's so vague how it's written that I might be completely wrong here.
-
The system in place is way too harsh -- if I've spent hours traveling into the map on one server and then that server either goes down or maybe goes to night and I'm not in the mood to play in the dark right now and I switch to a different server, there is no way I should be placed back at the coast and have to make that complete trek again. That is not a good solution to the problem. @Lt.Master it wouldn't matter whose base is it -- everyone would spawn outside of it, so if you log out inside of your base or your friend's base, you'd come back nearby it, just not inside of it. This could be a good situation especially if you're already geared and someone else has logged in before you and is trying to get into that base -- you'd spawn in close enough so that, if you had a scope for example, you'd be able to give the base a once-over before going to it. It's not a perfect solution by any means, but I don't think there is one for this problem -- other than making all the official servers private hives like community servers are. Spawning me back on the coast when I've already made my way all the way to Tisy, for example, is not a fair solution, I don't think anyway.
-
I think most people are in agreement that the current solution to server hopping is less than ideal. I do understand why BI did it the way they did it though -- if they respawned you by way of placing you some random minimal distance away from your previous position, that still leaves the possibility of people taking a guess, positioning themselves some distance away from a base and then logging out. It might only happen once every 50 attempts perhaps, but that still leaves the possibility of them logging back into the base. I thought of one possible solution to this -- having an invisible perimeter around your base that acts as a "no spawn" zone. This would reduce the displacement of respawns significantly. Here's an example of how this would work: The player finds a base on Official Server A. He logs out and logs onto Official Server B. He is in the same spot as he was on Server A since he was not inside of a base at the time. He moves into a position on Server B that he knows would be inside the base on Server A. He logs out of B and logs back onto A. Since he is now attempting to log into a "no spawn" zone due to the perimeter erected for that base on Server A, he is spawned 200m in a random direction from that point on the map. This would prevent players from spawning into bases, yet not displace them too far from where they were on the previous server. The perimeter itself could be restricted to maybe 10 square meters -- the idea being that you could place the center of the perimeter like you would place a land mine -- once you place it somewhere inside the base, it is surrounded by a 10mx10m grid with its center being wherever you placed the perimeter. Once placed, the server would calculate the 4 x/y co-ordinates signifying the 4 corner points of the perimeter and add them to the persistence files as "no spawn" zones, so that anyone spawning within that area gets randomly respawned 200m away. The perimeter device itself could even be an item that you must have looted to be able to erect the perimeter. What do you guys think of this idea?
-
Well, this is multiple bugs then. If you logged back into the same server, you should be standing exactly where you were standing when you logged out, because it's the same server! If you hopped to a hive server, you should only be moved randomly within say 1/4 of a mile from where you were standing before to move you away from a nearby base. Of course, this could lead to a random chance of you positioning yourself just far enough away from a base to get spawned into it, so I get why they are spawning you back on the coast, but that is way too harsh of a solution to this problem.
-
Clearly, Bohemia thinks your character needs to lose some weight there, young man! 😋 This is their solution for people trying to server hop into a base. It is a ridiculous solution which will hopefully be revisited and changed soon.
-
Bad version, server rejected connection
drgullen replied to JoaoZika's topic in New Player Discussion
So, the server you are connecting to is running a different version of the game -- they have perhaps already upgraded to 1.04 in which case since you're still on 1.03 according to the screenshot, you are not in sync with the server. To avoid this message, you must connect to a server running 1.03.151658 or if they are now on 1.04, you must upgrade your game to 1.04 as well. -
...or they'll just say fuck it and push it to stable with these issues still present. Why the hell even have an Experimental branch if this is the way you're going to do business? I don't get it -- the lack of QA going on here is baffling to me.
-
This is why I suggested you play on regulated, RP-type servers where punishment for breaking the rules happens -- on public servers, that is never going to happen, nor should it. The role of a developer is not to police the servers, waiting for someone to misbehave -- the role of a developer is to develop the game.
-
Fair enough, but my point is we've had issues in the past where a new patch produces unexpected glitches in similar situations regarding the menu or appearance of the game -- you would think testing how the game reacts after a server crash/restart would be a standard test prior to releasing a patch at this point, but apparently not.
-
Well, I've been called a fanboy and a cheerleader on here, but I'm not against criticizing as well and I really don't understand how we can be three iterations of 1.04 in at this point and there are still "menu showing in-game" issues. It kind of makes you wonder if anyone at Bohemia is actually playing the game as a test before posting a patch -- certainly doesn't seem like it, otherwise you'd think they'd have noticed that issue and fixed it before posting 1.04 in the first place. So yeah, it's not just you.
-
Well, they've released three versions of 1.04 so far and some of the bugs they said were fixed are still there, so they've got some bug-squashing yet to do with this patch before we go to stable. If you look at 1.02 -- it first went to Exp on March 25 and went to stable on April 3. 1.03 first went to Exp on May 10 and went to stable on May 27. If this pattern continues, it'll probably be sometime in early July before it goes to stable, but in reality, it'll go only when it's ready to go and it's clearly not quite ready yet. I think it's hard for them to advise when it'll be stable when they don't know for sure themselves. With any luck, we'll get another exp patch either Wednesday and/or Thursday and if it solves most of the current issues in this patch, perhaps we luck out a get a stable update on Friday. I wouldn't bet on it though -- I'd bet next week sometime.
-
@Mikaxo what you need to realize is that some people get off on using video games to act out things that they can't and would never do in real life. I would never steal a car, blow up a boat or shoot at the cops, yet I've done all of those things in Grand Theft Auto, for example. Some people take it a step farther, like you've described here. If this kind of behavior bothers you, I would suggest being more selective as to which servers you join. You might want to stick to role-playing type servers where the rules are more clearly defined and usually, strictly followed. On public servers or community servers with little to no rules, this kind of thing will happen to you and in a way, that's the beauty of DayZ -- you can make new friends that last for a long time or you can run into people that will resort to what was done to you. I'm not condoning the behavior, but keep in mind It's the internet -- the random encounters in DayZ could be anyone, of any age, anywhere. This type of behavior is usually rare, but ultimately inevitable.
-
This is an absolute guess, but what if you take the last | off the end? So change it from: hostname = "[MFPS]3PP|Spawnselect|Loot+|Traders|Enhanced Meds|FPS+|Fido-Mass-Squad|Hunting+|";// Server name to hostname = "[MFPS]3PP|Spawnselect|Loot+|Traders|Enhanced Meds|FPS+|Fido-Mass-Squad|Hunting+";// Server name If that doesn't work and if you haven't already, open a bug tracker ticket for this so that you can get help from the source with it.
-
Could it be a file permissions issue maybe?
-
My point was that Rancove asked for "a variety of military grade vehicles with some options to mount weapons". DayZ is not intended to be a military FPS game, that's what the Arma series is for. So, I doubt the devs are going to add a tank with a weapon mounted on it. Modders might bring that, but not BI. I would definitely like to see more methods of getting across the map quicker -- maybe a bicycle, a boat, a jeep perhaps and at least one type of helicopter. We are more likely to see those things added at some point.
-
I'm sure you'll get all those things and more...in Arma 4 whenever they make that game, but extremely doubtful you'll see it in DayZ.
-
Words are one thing, but I'm sorry, I don't want to be approaching someone's base and see, as their "welcome to our base" sign, a drawing of some sexual act, for example. If they allowed free form design, no doubt we'll see a lot of inappropriate content. Having said that, perhaps some type of mod that installs an approval system would work. Someone draws a sign and upon completing it, visually for now, the sign says PENDING APPROVAL or maybe is just blank. Once the server admin approves whatever the words or drawing are, the sign appears for everyone to see. Something like that would work, but would require active admins to check and approve/deny regularly.
-
Well, this is the PC section and I haven't played on console nor do I know how they have the servers setup, but typically M4s are rare in the latest patches I think, so look for a heli crash and you might luck out with one there.
-
Oh, I didn't know you'd reinstalled the OS already -- scratch that idea then. Hopefully, it works on the new drive for you.
-
I've googled this and everyone says deleting the profile in /My Documents/DayZ is the fix. I know you said it didn't work for you. This might be worth a shot -- uninstall DayZ, uninstall Steam, then reboot your computer, now create yourself a new Windows user on the computer (make sure it has Admin privileges), reboot again and log in with that new user, now reinstall Steam to somewhere other than /Program Files (I have mine as just C:/Steam) and then reinstall DayZ again. I'm wondering if whatever happened with your SSD issue somehow corrupted your Windows profile? I dunno, shot in the dark here.
-
Another way to look at this is don't delete anything -- the loot you are revising will change over time since most standard loot have preset lifetimes. So, for example, if you felt there were too many bottles of motor oil in the world, reduce its nominal, min and max values in the types.xml and after a short period of time, you'll notice fewer of them available to be looted. This way, you don't have to be deleting files or stopping/starting your server to change loot values.
-
If you mean preset signs, then I agree -- where you can choose from a list of signs like STOP AND WAIT HERE or APPROACH WITH GUNS AWAY OR RISK BEING SHOT or the like. If you mean custom signs where you can write whatever you like, then I don't agree -- it'll end up a shit show like in Rust where some of the signs end up as vulgarity or pornography. I like my porn, but I want it on my video player not in my video game. 😜