Rename lockstep to lofivor

build.zig.zon

@@ -1,5 +1,5 @@
 .{
-    .name = .lockstep,
+    .name = .lofivor,
     .version = "0.0.1",
     .fingerprint = 0x9de74c19d031cdc9,
     .dependencies = .{

docs/design.md

@@ -1,8 +1,8 @@
-# lockstep artillery game - technical design
+# lofivor artillery game - technical design
 
-a deterministic lockstep networked artillery game in zig with vector-style glowing line visuals.
+a deterministic lofivor networked artillery game in zig with vector-style glowing line visuals.
 
-## why deterministic lockstep?
+## why deterministic lofivor?
 
 bandwidth scales with input size, not object count. send "fire at angle 45, power 80" instead of syncing projectile positions every frame. replay files are just input logs. certain cheats become impossible since all clients must agree on simulation.
 
@@ -284,7 +284,7 @@ no physics libraries, no other third-party code in simulation.
 ## file structure
 
 ```
-lockstep/
+lofivor/
 ├── build.zig
 ├── build.zig.zon
 ├── src/

docs/reference.md

@@ -112,7 +112,7 @@ const len = try std.posix.recvfrom(sock, &buf, 0, &src_addr, &src_len);
 
 ```zig
 .{
-    .name = "lockstep",
+    .name = "lofivor",
     .version = "0.0.1",
     .dependencies = .{
         .raylib_zig = .{
@@ -138,7 +138,7 @@ pub fn build(b: *std.Build) void {
     });
 
     const exe = b.addExecutable(.{
-        .name = "lockstep",
+        .name = "lofivor",
         .root_module = b.createModule(.{
             .root_source_file = b.path("src/main.zig"),
             .target = target,
@@ -164,7 +164,7 @@ pub fn build(b: *std.Build) void {
 const rl = @import("raylib");
 
 pub fn main() !void {
-    rl.initWindow(800, 600, "lockstep");
+    rl.initWindow(800, 600, "lofivor");
     defer rl.closeWindow();
     rl.setTargetFPS(60);