Scouts and labs should not break tree groups
-
I'm against
how to resist this, make a scout or a lab that will kill your scout in the obviously necessary passage, there is no such problem on the gap, this is part of the game, part of the skill. Moreover, examples of 20km maps where this scout goes to the goal for 3 minutes.... and if it was not detected, this is the problem of the players, not the mechanics or the features of the faction. -
If it were added I’d rather it kept to a simple rule of “t1 units don’t break trees” than anything else.
Also it is pretty much functionally impossible to catch spirits on sentons before they get to trees regardless of player skill.
-
it's funny, but they are often caught if they know that the opponent with the best chance will make them
-
Literally Yudi’s team did it every single game in the last sentons tournament and they were never caught.
-
@ftxcommando said in Scouts and labs should not break tree groups:
If it were added I’d rather it kept to a simple rule of “t1 units don’t break trees” than anything else.
Also it is pretty much functionally impossible to catch spirits on sentons before they get to trees regardless of player skill.
What if we add an additional unit property here:
That indicates that the unit doesn't break tree (groups)?
-
I was thinking about some FACTION DIVERSITY to make some faction tanks break trees and some don’t and whether that would be good for the game or not. If that was decided to be good I think you would want that solution but I’m not sure if there is much of a reason for trees to be run over by t1 tanks and not labs as a universal thing.
-
Inb4 aurora and mantis don't break trees as they aren't real tanks.
-
I'm all in for the labs and scouts. But I think any other unit should keep doing so for asthetic reasons alone.
-
I dont really see the need to make labs not break trees. Never seen that been an issue
-
We should make LABs not kill engineers
-
I remember awhile back that broken trees were buffed or something so the reclaim value wasn't as big as a hit when broken to specifically combat this. Did this fix not work?
-
I wouldn't be opposed but I need to think about this a little more.
-
That's something that only impacts sentons/selkie as those two are only a few of the maps where tree breaking can really be harmful because of how abundant the tree density is and it's really hard to prevent an aeon scout from getting through because of how large the water area is and how open the map is which opens a lot of paths and sometimes it can be very unpredictable from where they will be coming from, the mechanic isn't particularly op for 99% of the maps but the environment of the map makes it so, i don't really think that's an issue otherwise the same logic can be applied for dual gappers who constantly complain about stuff like t3arty/nuke op but most people here tend to ignore those because they use the argument that they're irrelevant for 99% of the other maps.
-
Yeah, but this wouldn't really change anything for all the other maps (the LABs giving free intel to the enemy by breaking tree groups is a bug, not a feature. I wouldn't mind seeing it gone) while making it arguably better for Setons. That's not the case with nerfing Arties because of DG.
-
True, i gave random example though and there may be another more specific examples but yea ure right.
-
By that logic wouldn't reclaim changing because of enemy bombs without you scouting the result of the bomb hitting the reclaim also be a bug?
-
Honestly I would also like this change so that I don’t break my own tree groups and therefore don’t have to path scouts and labs around unbroken forests
-
@ftxcommando said in Scouts and labs should not break tree groups:
By that logic wouldn't reclaim changing because of enemy bombs without you scouting the result of the bomb hitting the reclaim also be a bug?
Technically - yes
.But that is a bug that is very difficult, if not impossible, to fix with the engine limitations.
-
Is seeing a lab through the fog of war that big of a deal? From the gifs I would have to actively look at that area to be able to notice the visual differences. That means I don't do anything else in that time, which is a pretty high cost. It looks like the main visual difference comes from different LOD values, can't we align them, so the tree group looks basically the same when it got broken?
Regarding the breaking of tree groups on purpose: People complain about build orders being too OP all the time. We have a tool here to disrupt the enemy's build order, but this is now unwanted too? I would like to hear some more explanation why you want to get rid of this mechanic. Do you take issue with the fact that the unit doesn't need to shoot to do damage? I think it's a creative use of the game's mechanics to counter a greedy build order and it's one of the very few options when your own build order is inferior.
If we still want to lessen the impact of broken tree groups we could play with the mass adjustment for broken groups. That has already been done once and that way we don't have to introduce additional complexity, where some units arbitrarily break trees while others don't. Plus we can keep the nice visuals of a lab crushing trees while running through a forest.
-
The way FAF uses tree groups is just a walkaround from how ugly the patrol or manual reclaim mechanics work:
-For patrol reclaim: engineer logic is fcked and for some reason they waste of lot of time to pack/unpack their claw between reclaiming multiple things.
-For manual reclaim: 1) You wouldn't click every tree manually which allows engineers to reclaim without claw unpack animation 2) FAF rejected all sorts of area reclaim and consideres it game-breaking mechanic despite such things exist in other RTS. (nobody misses stone clicking there, but i guess in FAF clicking stones is so much funnier than remaining SCFA gameplay)Instead FAF abuses attack move from factory - and that is actually a bug abuse which AFAIK didn't exist in GPG.
May be fix factory attack move and introduce proper area reclaim so people wouldn't waste half of their life clicking every stone on the map?
Some time ago it was more efficient to just break tree groups because it gave more mass, these days it better not to break trees because it is soooooooo much faster and gives more E. You have one number of trees, why do they give different amount of resources if they groupped of separated? All tree groups should automaticly break once game starts.
