| csThor |
02-22-2012 03:08 PM |
Quote:
Originally Posted by 6S.Manu
(Post 392985)
Of course, the right rules can solve that issue... maybe a "restricted area" warning like the one on the RO series. There needs to be a function inside the mission code. Otherwise you know that "smart" people will always find a way to go around that rule (flying on the border for example).
|
The FMB already allows the mission designer to set the "area of operations". Perhaps our code magicians can cook up a script that checks the players' coordinates vs the ones set as limits? And warns, and if ignored, kicks the player if he's outside of the assigned area.
Quote:
Originally Posted by 6S.Manu
(Post 392985)
And what if the map size does shape engine performance?
|
Okay, valid argument. You know back when Clod was just out and everyone had performance issues Ilya asked for ideas for smaller maps. Frankyboy presented possible maps of just the Straits of Dover and the area between the Cotentin peninsula up to Portsmough and Tangmere. Why those ideas weren't adopted I'll never understand.
Quote:
Originally Posted by 6S.Manu
(Post 392985)
It's a quantity vs quality matter: if I have to fly in that airspace (because of rules) why the developer has to model correctly places that I'll never fly above in those missions.
|
Well, I must honestly admit that I absolutely hate the canned appearance of Coop missions as they essentially kill the fog of war and any kind of surprise that may appear save for creative tactics of one of the engaged parties. I greatly prefer the freedom (timewise) the DF server style gameplay with heavy use of AI formations CloD theoretically allows. |
