"Unporkable CT maps?"

[Arlo]

Theory.

Since resets pork CT maps ....

... why not design the maps with the third country all bunched in a corner? 25 bases side by side way out away from the main battle area? And as a second measure, to assure neither of the remaining 2 sides are totally eliminated, we can put one base from each smack dab in the middle of the clump?

Wouldn't this:

1: Set up a small section on the map that is essentially unflyable/undriveable due to massive Framerate hits?

2: Set up an area that has tons of overlapping ack and aaa that doesn't creat a problem with ack and aaa being to tough on the rest of the map?

3: Even if someone tries to up from one of the active fields in the clump, they won't be able to get off the runway intact? Maybe even Tiger tanks won't get far?

The only possible problem I see is having one side or the other knocked down to just the field in the clump. Which really isn't anymore of a problem than we already have with map porking other than no reset involved.

[Dux]

Not a bad theory. Usually CT maps are leftovers from the MA or a scenario, so it would take quite a bit of retrofitting if not specifically designed for CT-only from the outset. And then that map might not be good for anything else.

But I think this may be a case of over-engineering the solution to a misunderstood problem. What exactly happened the other night to pork the arena so badly? Anyone know?

[Arlo]

On a side note about making a map unfit for MA. Wouldn't renaming the map actually make it a seperate map altogether and not render the original unfit?

[Arlo]

Originally posted by Dux
What exactly happened the other night to pork the arena so badly? Anyone know?

 Assumption is that an unknown group or individual milked one of the sides to a reset which forced a side rotation which porks CT setups. It's not an unreasonable assumption since it's happened before and the net result is what was experienced yesterday.

[Grits]

Or Skuzzy could have reset for some reason, or somebody could have taken one of the third country bases down in the SW corner.

[Mister Fork]

Any time a new map is loaded into the arenas, or end-of-month stats reset occurs, the CT arena is reset, as in our case yesterday.

[Dux]

Arlo: yes, renaming the map would make it a completely different map. I would never go messing with the original of a terrain.  


So whatever the cause was, the effect was that the arena as a whole reset, right? Fork (forgive my ignorance of setup), is there a "default" table that the map would revert to in that case, or does it revert to whatever the map was built as? If it is a default table, any way to lock or write-protect it?

[Skuzzy]

I reset the arena yesterday and reloaded the tables that were in it, but did not know about the country settings.  Ooops.

The problem with the countries changing fields is corrected.

[Krusty]

I don't think that would be a good idea, because whichever bozos are milking would milk all BUT that field, then peeps would join, be stuck in that horrible field, and leave in disgust. No, there must be another way.

I put a request in for a 2-sided map, a way of having a map where you are not FORCED to have 3 sides, to HTC a while back. Not sure how hard that is to code, nor am I sure if they'll ever do it, but it might ease the problem a little.


[EDIT] Is there a way to make a base "un capturable"? Meaning say you've got a map with 30 axis fields, right? Make the 2 rearmost fields "fallback" fields, that can never be captured, can never be porked... Or hell, maybe just make the rear most bases up the wazoo with flak so that NO enemy EVER will be able to take them. That way the one side being porked will ALWAYS have some place to launch from to re-take their fields.

I think that is a better idea than the original one (surrounding 1 with 3rd team bases)