Melding

TankHunter678

Well-Known Member
Jul 26, 2016
369
311
63
#22
Apparently many people did, enough for them to change the game design.
Could there have been other solutions? Probably.
The issue (I think) was that the AI server, and player connectivity, tanked during invasions. Leading to a higher amount of lag and the AI server breaking and requiring a restart when everyone online went to the invasion spot to defend.

People loved the mechanic, the technical side to make the mechanic run was not good enough.
 
Likes: DARKB1KE
Jul 27, 2016
412
472
63
#23
The issue (I think) was that the AI server, and player connectivity, tanked during invasions. Leading to a higher amount of lag and the AI server breaking and requiring a restart when everyone online went to the invasion spot to defend.

People loved the mechanic, the technical side to make the mechanic run was not good enough.
That too. There was number of things but I was explaining how the melding mechanic affected things overall.
 

Daynen

Active Member
Aug 3, 2016
184
246
43
#24
I enjoyed invasions in Beta, but there's one thing I didn't appreciate: after losing a POI and seeing the melding collapse on it, it just...opened up in a few hours. No interaction on our part, no re-opening the melding, it just moved back. I didn't see the point to that. It would have made more sense if we had to stage a 'counterinvasion' of sorts, dropping small melding repulsors outside town to open up a pocket big enough to let us reach the major repulsor inside and power it up before the mini-repulsors gave out, thus pushing the melding back en masse and allowing us to clear out the city of chosen...but I guess that day's passed.

The other thing I disliked about the melding was--you guessed it--retarded escort missions. The first time your VIP walks into the melding, you facepalm. The TENTH TIME? That's when you start blowing up the forums. I'm looking at you, Devil's Tusk.

It sounds as if we'll have a spiritual successor to the melding, so here's banking on the team understanding what was wrong with the original implementation.