This repository was archived by the owner on Jan 23, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathv1.4-struggles.html
More file actions
90 lines (77 loc) · 6.42 KB
/
v1.4-struggles.html
File metadata and controls
90 lines (77 loc) · 6.42 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
<html>
<head>
<link href="/style.css" rel="stylesheet">
<link rel="icon" type="image/x-icon" href="favicon.png">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<!-- HTML Meta Tags -->
<title>Sonic: Lock & Load » Horizons' Dev Hell</title>
<meta name="description" content="Detailing the history of Sonic: Lock & Load v1.4 \"Horizons\"' development and the challenges that followed.">
<!-- Facebook Meta Tags -->
<meta property="og:url" content="https://sonic-lockandload.github.io/v1.4-struggles.html">
<meta property="og:type" content="website">
<meta property="og:title" content="Sonic: Lock & Load » Horizons' Dev Hell">
<meta property="og:description" content="Detailing the history of Sonic: Lock & Load v1.4 \"Horizons\"' development and the challenges that followed.">
<meta property="og:image" content="https://sonic-lockandload.github.io/TITLEPIC.png">
<!-- Twitter Meta Tags -->
<meta name="twitter:card" content="summary_large_image">
<meta property="twitter:domain" content="sonic-lockandload.github.io">
<meta property="twitter:url" content="https://sonic-lockandload.github.io/v1.4-struggles.html">
<meta name="twitter:title" content="Sonic: Lock & Load » Horizons' Dev Hell">
<meta name="twitter:description" content="Detailing the history of Sonic: Lock & Load v1.4 \"Horizons\"' development and the challenges that followed.">
<meta name="twitter:image" content="https://sonic-lockandload.github.io/TITLEPIC.png">
<!-- Meta Tags Generated via https://www.opengraph.xyz -->
<script src="https://kit.fontawesome.com/56b6b2df41.js" crossorigin="anonymous"></script>
<title>Sonic: Lock & Load » Horizons' Dev Hell</title>
</head>
<body>
<div id="header">
<a href="index.html"><img src="Sonic-LockandLoadLogo.png" id="logo"/></a>
<hr id="separator">
</div>
<div id="content">
<a href="index.html" style="position:absolute;">⟨ Back to main page</a>
<h1>The History of Sonic: Lock & Load v1.4's Development</h1>
<p>I don't really feel like talking about v1.4's minor development hell, but I'm going to anyway.</p>
<h2>Before SAGE</h2>
<p>In the year of our lord 2022, before I knew of SAGE and SFGHQ, Sonic: Lock & Load was a small-time mod that was just hosted on GitHub. (still is nowadays, just not exclusively!)</p>
<p>By the time I decided to enter the project into SAGE 2022, I had just finished the v1.3.3 update.</p>
<p>Back then, Sonic: Lock & Load wasn't much of a fan game - it was more of a DOOM mod about Sonic, and an experimental one at that.</p>
<p>It was only when I decided to enter it into SAGE that I realised how much of a headache I was in for.</p>
<h2>SAGE 2022</h2>
<p>So, you remember SAGE 2022? How Sonic: Lock & Load was a part of that?</p>
<img src="sage2022.png" class="framed" alt="SFGHQ website screenshot, showing v1.4 'Horizons' at SAGE 2022">
<sub>Holy crap, the Final Final Demo has over a thousand downloads.</sub>
<p>Yeah, that brought more interest into this project, but also it gave me an insight on what I was doing wrong.</p>
<p>Unfortunately, instead of just let them have the broken and unpolished demo, I made three demos for Horizons. THREE.</p>
<h2>The Three Demos</h2>
<p>
The SAGE 2022 demo was literally just the unfinished v1.4 update with some stuff removed from it to make it feel more demo-y. <br>
There really wasn't much to it - it was just v1.3.3 with some much-needed polishes and a shiny new level. <br>
I pretty much only made the SAGE 2022 demo because I panicked and uploaded v1.3.3 to SAGE 2022 like an idiot. <br>
I really didn't put any thought into it.
</p>
<p>
The Final Demo was only slightly better than the SAGE 2022 demo. <br>
And by that I mean, it used a slightly less unfinished but still unfinished version of v1.4. <br>
Literally, it was the same thing - just updated, and based on a newer version of the update.
</p>
<p>
The Final Final Demo is where I actually started listening to feedback. <br>
This demo actually took steps to make sure that the game was more polished and ready for all those YouTubers to play and review. <br>
Which really helped - the alternative would be giving them the Final Demo or SAGE 2022 demo! <br>
Additionally, the Final Final Demo included a more new-to-DOOM-mods-user friendly package, that included a Sonic-LockandLoad.exe file, which was just gzdoom.exe renamed. <br>
<em>It was still hard getting people to realise you need DOOM2.wad or freedoom2.wad, though.</em>
</p>
<p>God, I'm glad I stopped at Final Final.</p>
<h2>After All That</h2>
<p>After the hype from SAGE had died down a bit, I decided I would actually make this update good, like, REALLY good.</p>
<p>I took feedback from people who enjoyed and didn't enjoy Sonic: Lock & Load - and I put those polishes and gameplay additions and tweaks into what would become v1.4 "Horizons".</p>
<p>No longer bound by a deadline once more, I took my time with this update. The Chaos Update (v1.0) had taken long enough in its own right to come out, but Horizons was looking up to take even longer.</p>
<p>And during that, I decided to promote Sonic: Lock & Load a bit more by creating pages on itch.io and Mod DB. The Mod DB stuff definitely helped to boost interest, especially with people used to DOOM mods.</p>
<p>I also ended up making a Discord server, which is currently rather quiet, but that's okay.</p>
<h2>Missing SAGE 2023</h2>
<p>Even more unfortunately, I got so involved in these changes that I forgot SAGE 2023 happened and completely missed it, which is why Horizons is slated for a November release, not September like I originally planned.</p>
<p>I just hope v1.5 will be a bit less chaotic.</p>
</div>
</body>
</html>