Player Features and Ideas Discussion

What is not the way it works? I've explained why it works and all the reply held was that I was wrong with no explanation.

Absolute speed is the hypotenuse in a right angled triangle where transversal and radial speeds are the sides, which all conform to the triangle rules that are well established.

Under the proposal one of the sides is capped by the web. At 0 degrees the hypotenuse is the same as this side. From then as the angle increases to 66.4 degrees the hypotenuse goes from the dimension of the side to another dimension (maximum speed) whilst the side is still constrained. The perpendicular side increases as well. At 66.4 degrees absolute speed is at max, radial is still at 40% (webbed), and transversal is whatever is needed. Between 66.4 and 90 absolute speed is max and the radial decreases. Transversal reaches absolute speed at 90 degrees. When orbiting radial is negative and is hence not subject to changes as explained in the OP.

This is also not a logical fallacy. Geometrical at most.

I am not changing maths. I am switching the sides of the triangle which are affected by the web. All other constraints are maintained.

Logical fallacy is the ambiguous replies you kids spout.

Make an excel graph if you want.

So, what you want is a web that controls how much the target can move towards and away from you?

So, let me get this straight... An orbiting ship (Ship A), under the effects of this web, would have it's actual, UI displayed velocity changed but it would not be going any slower around the webbing ship (Ship B)? Presumably without any change in orbital radius.
So, Ship A has a hypothetical velocity of 500m/s pre-web at an orbit of, hypothetically, 2500m. It is then webbed by Ship B and it's speed is reduced to 300m/s, it's orbital radius is unchanged, but it's still orbiting with the same speed? So, it is going slower and not going slower at the same time.

the web affects the max speed, and to be actually orbiting at 2500 in, say an interceptor, you're going at not nearly your max speed. The orbiting inty can take the hit to max speed because its already orbiting at the max speed its agility will permit while orbiting close. So its not going slower, but the ship has been slowed.

Viscosity physics aside

Absolute speed in relation to another body can be decomposed into 2 other speeds. One that is in the direction of the ship (negative or positive). As in if you draw a line from 1 ship to another ship. In this direction, the speed is called radial. Perpendicular to that is other component and its called transversal. If the angle is such that the absolute speed is in parallel to one component, then the other component is zero. This doesnt happen in practice because of viscosity physics and the prerequisites for orbiting, but thats digressing.

What I am suggesting is to make webs only affect the former component - the speed at which the ship can move away from another ship.

From your example, the ship orbiting at 500m/s will continue to orbit at 500m/s if its a perfect orbit. But if it changes angle and starts moving away from the aggressor, the speed at which it will be able to move away from him is capped to 300m/s. This doesn't mean that its absolue speed is 300m/s, just the speed in the direction of the line between the 2 ships. The transversal is the other component and in this example a maximum of 400m/s transversal could be maintained. This gives a radial velocity of 300m/s as your example permits, a transversal of 400m/s and absolute of 500m/s. The ship is moving at 500m/s, but only at 300m/s away from the other ship.

No math has been broken. If you put transversal and radial on your overview and check your speedometer you will notice similar things.

Would be obsolete because regular webs are better. Unless you expect people to orbit you (faster than with normal webs) and hence fudge up their own tracking.

Which is why I mentioned that it is food for thought.

Both methods can be appraised. Capping both directions or just 1.
In the case of both directions the web functions as a range constraint, and in radial terms functions exactly as it does now.

you realize that 7,500 m = 7.5 km right? thats only a 25% reduction? also frigates would be in much greater danger with a tractor beam pulling them in...

But thanks for the tip about prop mods... I never thought of that before! that should totally help my megathron catch that atron orbiting at 15 km /sarcasm

I think webs are too strong and have too short a range. They make brawler combat very binary: in web range = you can't move, out of web range = you're free.

I'd like to see web speed reduction brought down a notch, but have webs given a falloff which gives them a partial speed reduction at ranges greater than their optimal.

Howabout 40% speed reduction (t1) and 50% speed reduction (t2) with same optimal but 50% more in falloff? So T2 webber would have -50% target max velocity, 10km optimal, 5km falloff. At 15km the target would be slowed like 25%, and at 20km probably almost no slowing at all.



I've hit frigs enough times in my battleships. What doesn't happen as often is hitting a battleship in my frig. I think battleships have it way too easy against frigs. I'd advocate for more changes to make small, fast, weak-hitting ships harder to shoot down with big, slow-tracking guns. It's too easy at current. It's really not life or death for a battleship fleet if one frig has a slim chance of being missed, provided it flies in exactly the right direction to avoid fire. One false turn and a third of the fleet can hit the frig anyway, especially if there's some range involved. If you want to stop a frig from roaming through your battleship fleet, have your own frigs to stop it.


edit: just read title again. I read it the first time as webs reduce angular velocity (stop ships from orbiting) but now that I realize it's to stop ships from escaping while allowing them to remain fighting I LOVE it.

If you don't want to feel crippled by webs, don't let yourself fly in range of enemy webs. If the brawler got onto you, he deserve to slow you down to a crawl because you were outplayed one way or another.