refactor(flappy): use obstacle terminology instead of pipes
This commit is contained in:
parent
e5f544f103
commit
6b2778751b
3 changed files with 4 additions and 4 deletions
|
|
@ -104,7 +104,7 @@ export async function submitFlappyScore(input: {
|
|||
if (passes > 0) {
|
||||
await emitGameEvent(payload, {
|
||||
type: EventTypes.MinigameFlappy,
|
||||
message: `Completed a flight simulator run passing ${passes} pipe${passes === 1 ? "" : "s"} (definitely not Flappy Bird) (+${runXp} XP)`,
|
||||
message: `Completed a flight simulator run passing ${passes} obstacle${passes === 1 ? "" : "s"} (definitely not Flappy Bird) (+${runXp} XP)`,
|
||||
actor: user.id as number,
|
||||
targetCollection: "users",
|
||||
targetId: user.id as number,
|
||||
|
|
|
|||
|
|
@ -52,8 +52,8 @@ export default async function FlappyPage() {
|
|||
<h1 className="text-lg font-semibold">Flight Simulator</h1>
|
||||
</div>
|
||||
<p className="text-sm text-muted-foreground">
|
||||
An unofficial side activity. (Definitely not Flappy Bird.) Earn 1 XP per 15 pipes passed
|
||||
in a single run.
|
||||
An unofficial side activity. (Definitely not Flappy Bird.) Earn 1 XP per 15 obstacles
|
||||
passed in a single run.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ export function FlappyLeaderboard({ refreshKey = 0, currentUserId }: FlappyLeade
|
|||
<th className="px-4 py-2 font-medium">#</th>
|
||||
<th className="px-2 py-2 font-medium">Pilot</th>
|
||||
<th className="px-2 py-2 text-right font-medium">Games</th>
|
||||
<th className="px-2 py-2 text-right font-medium">Pipes</th>
|
||||
<th className="px-2 py-2 text-right font-medium">Passes</th>
|
||||
<th className="px-2 py-2 text-right font-medium">Best</th>
|
||||
<th className="px-4 py-2 text-right font-medium">XP</th>
|
||||
</tr>
|
||||
|
|
|
|||
Loading…
Reference in a new issue