Keep in mind that adding/removing caches and change the spawn time depends on the map and not gamemode, this means that is up to the mapper and any change requires the client to update his files, while only changing code requires no download and I'm allowed to mess with.
Brooklyn-Tech wrote:
Idk what "1 cache" would solve tbh. It would "dumb" the gamemode down to make it easier/more obvious/give less possibility for tactical decisions.
I don't like being killed in insurgency, weapon wise it's unbalanced but thats not why I hate the game, I feel that its not fair only one team having the power to decide when to attack or not.
With two caches you can literally be defending a cache for 30 minutes w/o a single contact and finally when you decide to move to the other cache or restart your IEDs you see yourself dead and a single guy taking the cache.
Having 1 cache, means that there will be no boring part, they (blufor) have to attack sooner or later. Maybe even adding a timer 45m to take a cache.
Brooklyn-Tech wrote:
*comparing INS with AAS*
You're comparing AAS with INS and there it is, people don't mind to be the ARF in AAS because they can "control" the game even without the cool kits in INS that's impossible.
Brooklyn-Tech wrote:
Also: 1 cache, same 1km/2km map from 0.97 and more insurgents due to 100m hideout radius all on a 100 player server. No thank you. Bluewhores gona sit back and whore even more kills.
Maybe, that's why we need to test.