[Devblog] The Future of Force Projection Feedback Thread

EVE… too much space - just not enough space to be left alone to do your thing… :pirate_flag:

I believe that’s by design, ansiblex are apparently only meant to move industrial ships around now (and possibly have them caught at the gate camps where they can’t jump back)

Being in a small alliance inside a small coalition I was concerned with being pressed into merging, I am no longer of that idea. Ansiblexes will become completely useless for CTAs, which is the only reason we have one in my alliance space. We will probably get rid of that (and reclaim the huge sov resources it consumes for something else) as our own space is decently connected. They can still be useful for alliances holding sov in badly connected space like long pipes, but that’s about it.

According to what I’ve read (and watched, with the YouTube video with FC Okami and FC Swift), there’s not going to be anything in-place initially to either increase the capacitor size or allow it to be boosted. The caveat being everything is very much subject to change, so take this with a grain of salt…

My $0.02 on this is that this is too severe a cut. They should probably implement a two-tier system:
• Continued use/requirement of fuel for all ships
• Capacitor (only) for combat ships
And I think the capacitor requirement(s) for the various combat ships needs to be revamped.

This change is basically CCP having 0 idea on how to make meaningful changes. Outside of Zone 1, Ansis are basically useless. Outside of Zone 1 & 2 they are useless. No one is going to include a Ansi, that might or might not be useable, in their route. They’ll just swap to “include jump bridges off” and take 30 jumps to move around.

If players have to spend half their daily game play time moving around, they’ll swap to capitals to jump. So this will ultimately mean less random PVP on gates and more structure to structure jumping. Until Okami decides that needs to be nerfed too. Okami started off with some good changes but he’s fallen into the Ratati trap of believing this game should be tedious and boring.

■■■■ tedious, ■■■■■■■ boring. Making a game hard != making it boring. Adding longer and longer travel time, does not improve your game in anyway. It just limits the amount of time players have to actually play.

2 Likes

Since we have the AT coming up in October and a major ship rebalance scheduled for the fall, I see this major update landing in the next 30-45 days.

Addendum: I just read September, so I guess I was pretty spot on.

I agree 100%. Currently, I do 3 jumps and I am at a market hub. With he change to ACL it will be 7. I will just load up a Capital and jump there after the change, but why make tasks more tedious and boring. When that gets nerfed I will just join the corp that allows me to use the ANSI again. This would only make a smaller group smaller and the larger group bigger.

That is the dumbest thing I have read in this thread, and there are lots of dumb things posted so far. They posted this information beforehand so that they can get feedback from people who actually play the game to improve and make this stupid idea work. Waiting until they release stuff and then try to improve a load of dung is not useful.

I would not move constellations apart but regions. A single constellation does not offer any useful gameplay loops for any group. You should be able to ansi around a region but not between regions.

1 Like

Poor you, whenever I need access to a Market hub, I usually have between 10 (everything below is considered excellent) or 30 jumps to make.

It is intentional that large-scale resource- and asset-movement should take lots of effort to make it worthwhile to use those resources locally to produce stuff out of the minerals and PI goods, refine and react them locally, build ships and modules locally, sell the stuff locally or use it for PvP action.

You should explicitly not mine millions of m³ in Ore, or PI mats and then just easily haul them over to convert them into quick ISK at some “trade hub”. The devs explicitly want to encourage decentralization and the best way to do that is to make it hard or costly to move lots of stuff over large distances.

If I have read that correctly, they use TJ (aka Terajoule) for the Ansis, which means a factor of 1000 higher values than normal Capacitor-Related modules in EVE use. So, even if the Ansiblex isn’t immune to captransfer, you would probably need dozens of FAX to pump them up with capacitor in a noticable way.

Nobody said that no feedback should be given. It’s just nonsens to doom-monger or judge the whole concept over numbers that simply aren’t final.

2 Likes

Why are they deciding what players do? The ansiblexi should be fully programmable like EVE Frontier.

Wouldnt that make it interesting, whether it operates fatigue or some sort of fuel OR capacitor depending on whats selected by anchoring peasant :slight_smile:

I think there is a fatal flaw in the mechanics of limiting Asiplex gates.

ACL allows only the most powerful Alliance members to pass through the gate. The designer’s goal is to have Alliance members use the gate only. However, it does nothing to place restrictions on characters. This means that if a character changes Alliance, they can use the gates belonging to that Alliance.

What happens if an existing large Alliance creates a “sub” Alliance row whose Ansiplex gates are always at a distance of exactly 1st category. Ansiplex takes approximately 5-8 minutes longer to move fleets of 250+ people per jump.

I am not familiar with zero sec mechanics, so I do not know how justified this solution is. This could be countered if there was a restriction per character that they are allowed to use “z” Ansiplex capacitors within “x” hours.

I suggest that “Z” here be as big as if it had traveled half a game space.

I translated this with the help of the google translate that was posted. This may cause incorrect text.

I do not think it’s practical for players to swap between alliances for every ansiblex.

I doubt that will be an issue.

3 Likes

Further, I would expect such an obvious abuse has already been considered and will be mitigated by some timer or other limit (ex. alliance change for ansi use applying at downtime).

1 Like

I’m assuming Ansiblexes are going to have some expanded access controls due to the extremely limited capacitor and the need to preserve it for emergencies.

man the conversations between the eve discord and here, are like opposite sides of the tracks, long time nullseccers like brisc rubal even praise the up coming changes and most of the ones on eve discord do… where as here… well.. nothing but the whiners.

1 Like

CCP used to tax the outputs of refining, now refining costs ISK. If the logic for the refine is sound, why not apply the same logic to the mining?

Farce Projection. OG jump fatigue was not liked because CCP boiled the frog too hard too soon. The ‘rich’ groups with depth of character roster avoided the mechanic entirely to just jump clone around the mechanic, its why people can only change clone school once every year now.

No, force projection is going to have to very different to what has been tried before for it to be of any value.

i just trying point out possible workaround. I not say its practical. My workaround is very non user frendly. Multi boxing 30 character to mine asteroid belts when 1 cycle /1rock got killed probably not player frendly game play. In the past many done it any way ( and not liked it ).

My opponion: Maybe only when this change go live we will see players do it in this mass scale or not.

The offical writings not contain any of this restrictions or i missed it. I not say they not going to add this type of limitation in future.

if CCP/FC add this type of limit it has negative side effects on new players who join a alliance. and not wish to abuse this loop hole This new player need wait x time before make use full of the null sov structures. The time when player wish to move in new home in null. Its bead game design in my book.

You’ve still got the issue of an extremely limited capacitor. I don’t see any way of skirting that. I can almost guarantee that any “creative” workarounds that go against the spirit of the Ansi changes be patched in short order.

1 Like

One of things I’m not clear on – is it the case that T1 freighters (which are capital hulls and don’t have jump drives) will no longer be able to use Ansis? If that’s true, what’s the logic of allowing Rorquals and barring T1 freighters?

1 Like