Since 21-6 is down, testing at classic...

Movement:
5 sectors: 1472 = 294ms per sector (move, kill, lay)

Pwarp torp: 30ms

Max response time: 20ms
Typical response time: 0ms

Pgrid:
Lift and stuff:
Elapsed Time: 49 ms

Move:
Elapsed Time: 283 ms

Layfig:
Elapsed Time: 59 ms

Landing:
Elapsed Time: 94 ms

So...

Ptorp is basically 30+ping. So if we target a 160 average,
that means 190ms response time.

We need to bump down the move delay by 20ms. That
would bring us to 260 move timing. That's a 70ms
difference. If we add 50ms to pwarp and 20ms to foton,
that makes up the difference.

But, how does that affect pgridding...

Pgridding is basically 150ms per. That would bump us up
to 200ms, give or take. Adj photon would be ping+photon
delay, or 170+50 (about 30ms currently) or 220.

I actually think that would work pretty well, since someone
w/ a faster ping or a slow pgrid burst would even the odds
a bit.

So for the next round, I'm going to recommend:
Remove 20ms from move delay somewhere
Add 50ms to pwarp (before the pwarp)
Add 20ms to photon (before the shot)

Would like to test them again afterwards, would help make
ICE more balanced next month.

Edit:
Bwarp - Currently takes about 30. Can we add 50ms to this?
Xport - Can we add 20ms to a post-xport delay?

I'm just about ready to post an update to classictw.com that will include all of the timing settings so you'll be able to explore all of these settings yourself. I added a few more synch and delay options, so there are probably more now than you need. I put in plenty of room for expansion, so if you need anything new added, I can easily drop it in.

Sounds good.

Couple questions...

Other attacks? Is that attacking figs?

Ship IG, is that turning on IG or holding in IG?

Transport, is that tpad or xport?

If xport, is there a tpad control?

Photon trigger, is that photon delay? Or?

Oh, and CIMs are still timing out. (^IQ)
Is there a way to adjust that delay?

I don't have the problem locally, I don't have the
problem on pre-beta. I didn't even notice it on 21-6,
altho I didn't get a lot of time in there. I notice it a
lot on ctw, tho.

Even if others don't have the problem, would like
to test out different CIM delays.

"Other attacks? Is that attacking figs?"

That's any attack other than ship vs ship. So sector fighters, planet fighters and shields, colonists, beacon, I think that's it. I figured I could roll it all in together, but if not, I can split some things out.

"Ship IG, is that turning on IG or holding in IG?"

I'm not even sure how a delay for holding would work. It's for powering up the IG, when you turn it on. And when a delay is specified, the IG will automatically power down whenever the ship moves, so you have to power up again at your destination. When no delay is specified, there's no change in how an IC works.

"Transport, is that tpad or xport?
If xport, is there a tpad control?"

Both. I split that into ship and planet xport for pace times, but I left it as one value for both in delays. I should probably split that up because they're not really the same thing.

"Photon trigger, is that photon delay? Or?"

You have both Photon Launch delay and Photon Trigger delay. Trigger is a delay between the time the Photon enters the sector and you get a message that it's there, and the time the Photon actually detonates and has an effect. I haven't actually implemented that yet. But when these delays are set to zero, there won't be any change to Photon functionality.

"Oh, and CIMs are still timing out. (^IQ)
Is there a way to adjust that delay?"

I didn't add a pacing time for CIM output. I guess I could do that, but there will be three different values to set for CIM, or else I could set a factor to set all CIM delays at 2x or 1/2x or whatever. But I don't think that's the problem, because the pacing on these is the same as it was. There's something else going on here, but I haven't been able to witness it myself.

Ok, I posted a new update. The transport delay has been split into Ship Transport and Planet Transport. Also, both of these delays include a "linear" option like the one used for Planetary Transwarp, so you can have a delay that depends on transport distance.

I also put in code to support Photon trigger delay. If trigger delay is <> 0, a message is sent to the target sector that a Photon was just launched into the sector. Then, after the trigger delay, another message is sent stating that the Photon just detonated. At that point the Photon effect begins. If trigger delay is 0, there is no change in how Photons work.

Let me know if you have any issue with these settings.