Forums » General
Border Skirmish
Just a heads-up: we have Deneb B13 (the Border Skirmish sector) running by itself on a dedicated machine at the colo, with a lot of new logging stuff enabled. Hopefully this will help us track down whatever is happening. Anyway, if you see it acting bizarre (over the coming days), feel free to post here.
Hive Skirmish may still show strangeness, we're just debugging the one at the moment, hopefully the issues are related. BS is a more ideal single-sector test, where HS is much more dynamic and distributed.. more complex for us to set up like this.
Hive Skirmish may still show strangeness, we're just debugging the one at the moment, hopefully the issues are related. BS is a more ideal single-sector test, where HS is much more dynamic and distributed.. more complex for us to set up like this.
Okay. Yay! um... I almost had to post in the Bugs forum stating that the central Sedina Hive lagged so much that I couldn't jump out, and then log in.
You may want to fix that, somehow...
You may want to fix that, somehow...
Cap ships seem to go down awfully fast. Especially the Serco HAC which attracts a lot of attention while I often see the Itani HAC sitting by itself though that could just be a coincidence.
From what I've seen, most damage to cap ships comes from other cap ships exploding on top of them. If the explosion is big enough to take shields down, perhaps a greater concussive effect to push other ships away from the explosion and avoid snowballs of death which are fun to watch but not much fun to participate in (the cap ships are what make the BS fun, if they die too fast, less fun). Better distance control on the part of the cappies would help too.
Itani really seem to have an advantage in reinforcements. More often than not Itani cappies will outnumber Serco by three or four. Again, not always but often enough that it is frustrating.
Maybe the Serco could get a few HACs on the Deneb side of the GR wormhole for repairs/rearming until Deneb goes grey and assumedly the station imbalance is addressed.
NPCs are far more aggressive which is good. But I get rags chasing me with missiles when they should be targeting the cap ship (at least I assume that's what they should be doing).
I don't think any of these points are new but since it's a new thread...
From what I've seen, most damage to cap ships comes from other cap ships exploding on top of them. If the explosion is big enough to take shields down, perhaps a greater concussive effect to push other ships away from the explosion and avoid snowballs of death which are fun to watch but not much fun to participate in (the cap ships are what make the BS fun, if they die too fast, less fun). Better distance control on the part of the cappies would help too.
Itani really seem to have an advantage in reinforcements. More often than not Itani cappies will outnumber Serco by three or four. Again, not always but often enough that it is frustrating.
Maybe the Serco could get a few HACs on the Deneb side of the GR wormhole for repairs/rearming until Deneb goes grey and assumedly the station imbalance is addressed.
NPCs are far more aggressive which is good. But I get rags chasing me with missiles when they should be targeting the cap ship (at least I assume that's what they should be doing).
I don't think any of these points are new but since it's a new thread...
Cap ships seem to go down awfully fast. Especially the Serco HAC which attracts a lot of attention while I often see the Itani HAC sitting by itself though that could just be a coincidence.
This is because the devs haven't fixed the warp-in points for the non-HAC ships. Itani capships should warp in near the Itani HAC, and Serco capships should warp in near the Serco HAC, not all of them warping in together into a big ball of laggy fail.
Itani really seem to have an advantage in reinforcements. More often than not Itani cappies will outnumber Serco by three or four. Again, not always but often enough that it is frustrating.
This is more a function of the Serco capships being destroyed more quickly than the Itani ones; each type of capship has a set "respawn timer". Because Itani players show to the Skirmishes more frequently and in larger numbers than their Serco counterparts, the Itani capships are better defended and take less damage than the Serco capships, which are forced to not only take the usual beating that they would get from the Itani capships (note that, likewise, the Itani capships also take this punishment), but the determined thrashing from the Itani players. If more Serco players showed up this would probably even itself out.
This is because the devs haven't fixed the warp-in points for the non-HAC ships. Itani capships should warp in near the Itani HAC, and Serco capships should warp in near the Serco HAC, not all of them warping in together into a big ball of laggy fail.
Itani really seem to have an advantage in reinforcements. More often than not Itani cappies will outnumber Serco by three or four. Again, not always but often enough that it is frustrating.
This is more a function of the Serco capships being destroyed more quickly than the Itani ones; each type of capship has a set "respawn timer". Because Itani players show to the Skirmishes more frequently and in larger numbers than their Serco counterparts, the Itani capships are better defended and take less damage than the Serco capships, which are forced to not only take the usual beating that they would get from the Itani capships (note that, likewise, the Itani capships also take this punishment), but the determined thrashing from the Itani players. If more Serco players showed up this would probably even itself out.
We're looking mostly for cases of where you're able to hit other ships but not get a returning beep, where ships start drifting and not shooting, etc. Not so much BS "game balance", which is another issue and not really related to the fundamental technical issue that seems to be sporadically occurring.
The trouble is, most of the same symptoms occur with a high "ping", ie.. to people off of North America (our Aussies, etc), or to people who are just impacted by internet weather of one kind or another (a route going down here or there). So, please post the output from /ping at the time when you saw the problem.
The trouble is, most of the same symptoms occur with a high "ping", ie.. to people off of North America (our Aussies, etc), or to people who are just impacted by internet weather of one kind or another (a route going down here or there). So, please post the output from /ping at the time when you saw the problem.