Gagzila, on February 07 2013 - 05:45 PM, said:
NBShoot_me, on February 05 2013 - 01:18 PM, said:
Server side options can mean two things here, so you need to be specific (EDIT: I'm talking about where it's enforced, not the setting itself so much, well separately, two pronged argument on my part).
Your edit just undid the specificity of your original comment. "not the setting itself so much, well separately, two pronged argument on my part", sorry but what do you mean_
When I talk about a server side option - the host starts a new server and they have an "forced on / forced off / variable" option for forced screen shake. It should be a single set level of what is available from the slider, the devs would need to decide an initial level and then review community feedback. Say for example it is set at 70%. A host starts a new server and sets the forced camera shake option to "forced on", everyone joining is then forced to have 70% screen shake turned on. If set to "variable", then players joining are free to have the slider manually adjusted to whatever they want, including off. If set to "forced off" then everyone joining will have screen shake forced off (since we need to cater for the other side of the forced on coin).
Been a little while since I’ve read this whole thread, so sorry if I’ve lost my place.. working on some SQL / APACHE / PHP stuff ATM, so I might sound a little aloof.
The edit means what it means. I’m trying not to tunnel vision on this one, because if I do I’m either in complete disagreement over a “hardcore” mode or in a partial agreement with a “hardcore” mode. But, to attempt to clarify:
When you argue server side options that are configurable, you can be talking explicitly about the options themselves, like the camera-shake configuration, bloom, or really any configurable option in the game. You can also be talking about the enforcement side, which is where game filter option via MM, or server browser filter. Sorry, I just really tend to overcomplicate this stuff.
What you describe would be the latter (server browser filter), though, which is the method I’m least opposed to. What you describe however does raise some concerns on my part though. Mostly, what other configuration options should players be allowed to enforce when they start a server, I seriously doubt it’d be worth the ADH’s time to work on said functionaliy for JUST camera_shake.. but where does the line on what you can enforce get drawn_
Gagzila, on February 07 2013 - 05:45 PM, said:
NBShoot_me, on February 05 2013 - 01:18 PM, said:
Server side could mean that there is a pool of “hardcore” servers that MM attempts to populate, or it could mean that there are servers started by players (via server browser) that have a “hardcore” or just simply custom restrictions put into place. I’m against anything that affects the already broken MM directly. As for something that is implemented in the server browser, I’m fine with that.
I thought we just agreed that this won't work with MM. Yes, wait for the server browser to come back. Also forget about discussing a hardcore mode as it's only clouding the main topic, we are discussing the merits of a server side option for forced camera shake.
I’m simply clarifying here, but when you get to my second paragraph, why I brought up MM again should then be more apparent. And yes, I am running under the assumption that we’re in agreement that this won’t work with MM. The reason I am still referencing a “hardcore mode” is also hopefully covered in the second paragraph, though I’ll clarify in a moment on that.
Gagzila, on February 07 2013 - 05:45 PM, said:
NBShoot_me, on February 05 2013 - 01:18 PM, said:
Once the server browser is back, servers with restrictions could be designated by an icon and/or via a server filter option. Basically, how it’s been done for years in gaming. And if servers listed in the server browser are eligible for players who deployed via MM, I’d have any custom servers excluded from that pool. But honestly, I’m not sure how granular these settings should be. How many and what settings could be, or really, SHOULD a player be able to enforce upon others_ Worst case scenario for the player; he/she sits around in an empty server for a long while. For Adhesive / meteor, they could end up with a heavily splintered community that might //EDIT// not //EDIT// grow.
Agreed.
Also you should look at it from a POV as the host enforcing settings on the server and players CHOOSING to accept the rules of that server by joining...no one is forcing them to join and play by these rules.
And for the last time man, this would be implemented down the track when / if Hawken gets big enough
Cheers,
Gagzila
Well, I think I touched on the host perspective a bit, and that basically boiled down to the hosting player’s perspective followed by the possible overall impact on the community. And while I have no problem with the model where a player agrees to, though is still forced to abide by a host enforced configuration, I’m more concerned about which configuration options, or more to the point, how many should be available to a hosting player as far as enforceable options go.
Also, MM was brought up because I wanted to be very clear, that I didn't want ANY custom game modes affecting the server pool used by MM. I didn't and still don't know if servers listed in the server browser could be populated by MM.
The hardcore mode I referenced earlier would come into play here. The idea is nothing new, but basically, an established set of configuration options or other restrictions that constitute either a more level playing field or more realistic-ish experience depending on the implementation. This would be the route that would allow for people to feel the least cheated by others, but at the same time not end up with a sizeable portion of the servers all having a wide variety of different config enforcement rules, because remember, we’re talking about camera-shake now, but you and I both know that actually going forward with the idea would include much more than just camera-shake. This is where the concern over a splintered community comes from, and it *can* hurt even a more established and large community if there is not continuity from one server to the next as far as what is considered acceptable / allowed. The isn’t Half-Life where you used to have thousands of community run servers ranging from vanilla to low gravity unlimited funds “fun” servers (CS mod). .. though I wouldn’t mind doing away with the thruster vmax.. but that’s off topic.
One tidbit that I mentioned a while back (I think), concerning enforcement from the host perspective (more of a ADH issue really..) would be making sure enforcing camera shake on (in the scope of this discussion) results in players actually playing with camera shake on. Movement restrictions, accuracy restrictions, heat restrictions, and all that can be enforced server side just fine, but forcing a client variable_ NOW you’re getting into the area where people can more easily hack something like this. To truly be partially sure that people are abiding by say.. camera-shake being forced on, you’re going to need some form of cheat-detection in Hawken.
Back to my ini files and SQL console!