From 21886c00a845cc7b9b823bfcff37988950ba8668 Mon Sep 17 00:00:00 2001 From: Tangent Wantwight <tangent128@gmail.com> Date: Sat, 15 Feb 2020 13:55:33 -0500 Subject: [PATCH] Remove TickType idea --- src/Ecs/Lockstep.ts | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/src/Ecs/Lockstep.ts b/src/Ecs/Lockstep.ts index 1a70613..71e42fa 100644 --- a/src/Ecs/Lockstep.ts +++ b/src/Ecs/Lockstep.ts @@ -17,18 +17,6 @@ function equals<T extends Equals | string | number>(a: T, b: T): boolean { return (a as Equals).equals(b as Equals); } -// TODO: probably an incoherent idea. Instead consider having two state objects, -// a synchronized state object that can be rolled back / predicted, and -// a cosmetic state object that glosses the synchronized state and never rolls back -export const enum TickType { - /// a "canonical" update that will not be rolled back; - /// this must be fully deterministic based on the state and input. - CANON, - /// a "predicted" update that may or may not be rolled back; - /// if possible, avoid changes that could be distracting if rolled back. - PREDICTED, -} - interface LockstepProcessor<Input, State> { compareInput(a: Input, b: Input): boolean; cloneState(source: State): State;