They are so uncommon let's take a second to appreciate SNES games with functional loading screens.

Game: Civilization 1
Loading time: ~40 seconds
Purpose: When you create a new game. It is procedurally generating the terrain of the map, placing the other civilizations you're playing with. Rather than a fixed map, it gets randomly generated each time plus the algorithm is customizeable to include different kinds of climates and features. The longest load time I have seen on this platform.

A video: https://youtu.be/oWtVe2qm7_w?t=129 (not mine, random search off youtube)

Game: Romance of the Three Kingdoms IV: Wall of Fire
Loading time: 2 or 3 seconds
Purpose: When you create a new game. Procedurally generating what commander has what resource allocations, which officers are where. Although the game comes with a fixed set of "scenarios", you can create your own commander and/or officers and choose who to control. I believe this, plus the difficulty level affects where the game places things and there are too many combinations to pre-compute them.

Game: Another World (also called, Out of this World)
Loading time: ~10 seconds
Purpose: Transitioning out of a simple menu, into the game

This game is, in a word, ambitious. Big, lush backgrounds with lots of things animating. Nothing looks like 'sprites'; they look like 2D vector graphics rasterized to low resolution to be honest.

This game was originally for Amiga and ported to SNES. The graphics have a unique style which unfortunately doesn't fit well to SNES technical constraints, which tend to involve either conventional 2D graphics modes with heavily re-used sprites, or just Mode 7-- neither of which fit this game well. Now that's not to say it can't work. Take, for example, the backgrounds of Super Mario RPG or Wonder Project J. You can make smart judgments about when to re-use sprites and try to hide them among the other elements. Of course, those games were designed from the ground-up for SNES. For this game, conversion to sprites would be an after-thought with the port. The sheer amount of graphics this game has is very large and scenes are organized in ways that are hard to break down into patterned elements.

While I don't tend to like this type of game- the latency of controls is so slow and loose, for one-- I respect its commitment to the unique art style. Given everything this game has going on, the loading screen is not frivolous.

Game: Sim City
Loading time: ~12 seconds
Purpose: When previewing the terrain on which to build your city- there are 1000 terrains (e.g., random seeds). Note that the load time is NOT just for creating a game with the level- it's to let you view a small 120x100 image. This, plus the instantaneous "OK" button tells us two things. First, there was not enough space on the cart to store 1000 of these images. Second, unpacking the preview image is about the same as unpacking the full map. While I think all of this is okay, they could have done with fewer better-optimized seeds. Fortunately the instruction manual has a couple pages of previews of maps which you can flip through quickly.

Game: Batman Forever
Loading time: ~5 seconds
Purpose: Transitioning out of cutscene into gameplay. Likely to be graphics-related. There are big, detailed sprites with lots of frames of animation.

Although there's an explanation for a load screen, it may not have been completely necessary. At 24Mbit, the cart is not that small; it's very likely the graphics could fit without super aggressive compression schemes. Some contributing factors to the need for load time may have been 1) the fact that this game is a port, and there wasn't time to optimize for any particular platform, and 2) these flashy 3D wireframe-map montage scenes, which would require different types of data and loader code.

Although this game gets a bad rap I respect its live-action-to-low-res-low-color Mortal Kombat aesthetic.

Maybe others I haven't encountered yet.

See, a couple big things affecting our modern conception of loading screens are optical media and network latency's failure to keep up with increasing size of game payloads. Computationally, modern computers have advanced a lot to the point where it is rare to see games spinning on procedural content like this, but it is common to spend a lot of time copying game assets from an optical medium to faster local solid-state storage, or downloading game assets from the internet.

There have been some modern efforts to curb load times. For example the Nintendo Switch had a return to a faster-than-optical-disk game media. You know, a cartridge. However, many Nintendo Switch games- non-procedural, fixed-level action games do have loading screens- screens which would have been unacceptable in 1995 but are acceptable now since we are used to them.

Earth, who wore it better?

left: E. V. O. (SNES) right: Civilization (SNES)

Finished Donkey Kong Country 2: Diddy's Kong Quest. This was a co-operative gameplay I finished with a couple friends as a follow up to our completion of Donkey Kong Country 1.

Completion time: about a year, since we played in small increments once in a while.

Game is longer and a lot spicier than 1. Some levels gave us a very hard time. Yeah I am a big fan of the minecart autoscroller.

Time and time again I am really impressed by how much graphics can be fit on a SNES cart. The levels are all full of lush, irregularly-shaped (non-tiled-looking) elements without a lot of repetition; sprites are big with lots of animations, lots of frames in each one; backgrounds have a lot of variety. At the same time, it also doesn't appear they got too fancy with storage of graphics. I looked at the ROM and could spot at least some 4bpp graphics data stored plain, uncompressed. They just used a big cartridge-- 32mb, big for this console.

The technical high points for this game are offline rather than online of course. These are pre-rendered 3D models rendered with Silicon Graphics software, likely on CPU, baked into a bunch of 2D sprites. Everyone likes this. I can't think of a single fourth-console-generation game which does this and looks bad. More games would have surely done it if it wasn't so expensive back then, in terms of money.

Only criticism is I was disappointed with the final boss fight. The fight from DKC1 established a pretty high bar, to be fair- it had that cool "fake credits then surprise there's more". Not saying DKC2 had to replicate that, but maybe the final boss could have had something else cool. Nope. You fight King K Rool on a pirate ship. He throws projectiles. Pretty standard stuff. Maybe they thought no one would get far enough to see that, due to Windy H̶e̶l̶l̶ Well.

You know, tetris?

Computers can be used for many things. Reading books, watching sports games, communicating with others. In your life, you may even come to play some games on your computer. Some of those games may have been good. Some may have been fun. This is not one of those.

This is the game as usual with one thing changed: the camera is locked to the current piece in flight. It moves along with the piece, and rotates too. Suggestion: appreciate the concept but do yourself a favor and don't play it

https://github.com/clandrew/sirtet/

One of my favorite retro sports games is Ice Hockey for the NES. This game gets overlooked because it's on the simplistic side and not tied to a real-life franchise, but it's still a good time.

I started getting into watching hockey streaming so I've been playing this game as something to do during intermission or when waiting for the game to start. One thing led to another and I ended up making a romhack to change the sprites over to be female looking.

Before:

After:

Some more gameplay

Here's a demo of using the tool for simple task of crossing-out the puck sprite

Instead of crossing out the puck I made other changes to the sprites of course, and used this tool to import them back into the ROM.

Ultimately it may have been possible to use someone's already-made tool in lieu of making a new one. I tried one, YY-CHR since it's popular. But, I had problems getting it to understand externally-pasted or externally-imported images, and YY-CHR's built-in image editor was not sufficient for my workflow. If that one didn't pan out, it may not bode well for the others. Since I was familiar with the image formats it was not too much to simply make a new thing.

About this game's mechanic, if you aren't familiar- this is 4-on-4 hockey. Skater players come in three varieties: light, medium and heavy.

• The light skater is fast but has a weak shot and can be knocked over easily.
• The heavy skater is slow but has a strong shot and tends not to get knocked over.
• And, the medium skater is in the middle.

You pick what type your 4 players should be. A typical game involves a balance of skaters, although ultimately it's up to you.

The players, ref, goalie and zamboni driver are edited. 👍

To play it you don't need to use the tool, of course. I'm posting a patch so you can just patch your ROM.

Click here to download the patch (IPS). Patch was created using LunarIPS. LunarIPS is also recommended for applying patches. Apply the patch to an unzipped, NA release ROM, size 40976 bytes. Don't hesitate to contact me if you want to play but don't know how any of this works, I'll set you up.

And click here to download the source spritesheets if you want them for some reason.

If you want to change the sprites to fit your own creative inspiration, you too can use the tool I made, posted to GitHub here.

Update (1/15/2020): Fixed missing bun in one frame of heavy player animation, fixed back-of-ref's-head-during-penalty animation

Finished Code Vein (PS4)

Visual style: modern JRPG
Gameplay: Souls-like

The game takes place in a dystopic future where vampires were created to fight in a war against an evil force. Bad news #1 The government is trying to get ways to harvest blood to sustain the vampires, but it's not going as smoothly as they hoped. Bad news #2 the evil force is not really gone.

One innovation they added is a 'companion' system where an AI-controlled NPC accompanies you basically at all times. The AI is competent and not a liability like in some games.

The game improves on Souls in some areas.
- Online matching system. Match with anyone! Your and their levels are scaled to match so it's fair.
- The class system makes it so you can't irreparably screw yourself through uninformed decisions.
- A map
- Healing item cooldown makes it harder to accidentally waste heals
- AI is 'smart', doesn't randomly jump off ledges.

I was nervous they might have strategically put the best environment in the demo I played. But, no, the demo was representative. The environments were consistently good. Big complicated areas, detailed rooms without copypaste, interesting stuff to look at far into the horizon.

Although the game is not perfect (nothing is, right?), no one in the art team seems to care about CLIPPING, as far as I'm concerned it's a 'perfect score' game. It doesn't happen every day there something which takes so many interesting risks, turns, stylistic decisions.

Although I did 4 playthroughs I still want to do some more things. A bunch of the replay-ability comes from the multitude of classes ('blood codes') and multiple endings, which range from 'uplifting' to 'stomp your heart into a zillion pieces'.

The game is a bit violent and sleazy so maybe not appropriate for all audiences. But it is really good. I hope there will be a sequel or DLC.

I made a tool for converting a spritesheet into an animated GIF.

This program was borne out of a similar situation as the text editor one. I needed some functionality that was super simple but couldn't find exactly the right thing in an existing program.

I used to use a web application for doing work like this, but I don't like depending on web apps where it's not strictly necessary. Why, because when you upload your files or data somewhere, you're putting a lot of trust in that other party. They probably wouldn't mis-use your data, and the data isn't anything sensitive anyway, but the principle of it is undesirable.

There's also the fact that a web application is so much overkill for the task at hand. Think about it. Why do I need a full web stack, javascript interpreter, communication across text protocols, etc for something so simple like resizing an image, or changing the encoding? It boggles the mind. It's like SHOUTCLOUD but not ironic. I have nothing against web applications, but I don't think everything needs to be a web application. That stack is too thick.

As for the whole world heading to web applications, maybe that's inevitable. This idea could become feasible as internet infrastructure improves- in many countries it is not all that fast or always-on-and-everywhere, right now. The principle of a thin client with a smart server and a good internet connection seems interesting.

But why do these this future "web app" need to run in a browser? Why does it need to be built on HTTP, of all things? Remember, there's a difference between "internet" and "web pages". There was internet before web pages. There might well be internet after them. What is so holy about HTTP? It's hard to see anything good or holy about it, other than it's a standard (ish!) borne out of 2 decades of blood and tears. If you've had to do any work on a web browser, you'd know. I did a little. I've seen enough.

Indeed, a thin client can't even be all that thin if it can parse and display web page content. HTML5+Canvas, CSS, JS, SVG, weird extensions and back compat... there are a lot of sub-technologies required to get a competent web browser and light up even basic, typical scenarios. A lot of things could work via a simple page but in practice they do not. In the late 2010s it's not uncommon to see >10MB payloads for viewing a single site, and for pages where that payload isn't all images or video- pretty common- you can imagine the CPU necessary for unpacking some of that.

Put it all together with the fact that local computation, device battery life and internet connectivity haven't really kept up with rising web site complexities. If they did, none of this would even be a problem. I wanted to hold some optimism for here for phone apps but I highly suspect they're usually coded as web applications, hosted in web browser containers anyway.

It's nice, the idea of side-stepping that entire stack and running a program natively on your computer. If the program was written competently, it has a good chance of not being flaky. At least, it is not likely to be screwed by tech on which it is built.

Web pages are good for some things, things based around displaying text and images which are updated remotely. Maybe some light games. But you should probably not run your traffic lights, your pacemaker in a web app.

Anyway, as for this program- it runs natively, and includes some features that are useful for what I needed out of it.

Find it here on GitHub.

A cool (and hot!) boss fight in Code Vein. Guest appearances from Louis and random internet person.

Am I the only one annoyed by the phrase "buttery smooth UI"? It has this tendency to mean "unnecessary transitions, 2D graphics with surprisingly high cost"

Total play time = 2 years, 156 days, 20 hours, 36 minutes, 39 seconds

Couple friends and I started playing back in April 2017. The progress isn't deliberately slow, it's just that we playing a half-hour or an hour here and there, once in a while and it's a proper full-length RPG. Furthermore we made a best effort to play it spoiler-free with as minimal outside help as possible.

I never beat this game before. SoM is in the category of "played as a child by repeated rental, wanted to own, couldn't get a copy".

It is hard nowadays imagining "not being able to purchase something" but was the situation here. If no video or toy store in our city had it then out of luck. There were also toy catalogs where you can phone or mail in an order, but they weren't a whole lot better in terms of the video game selection. The one place I could find that had Secret of Mana had it for rent. So I rented it repeatedly. I still had to take it back at certain intervals and some jerkface wiped my save. After that I became demoralized and moved on to playing something else (Uncharted Waters 2)

Fast-forward to today and I have every game in the world. This one has a lot of critical acclaim, and still has some love today (it got a remake last year), it deserves playthough to the end.

Originally I thought I'd move onto the remake after finishing this, but after reading some reviews, maybe not 🙁 It's just as well, initially I was kind of turned off by the graphics. When early gameplay came out I recall telling people it looked Bad. Like some free-to-play MMO from ~2006. It reminded me of Audition Online. I don't know what's up with the art direction. Apparently there are problems with the soundtrack and gameplay also... How did they mess this up? I may someday play it anyway but give it a while.

This game had a lot of positive qualities, it deserves to be on all those top-10 lists. 
- The soundtrack is very strong
- Large sprites with nice animations
- Many cool concepts for bosses, large enemy artworks
- Willingness to make a three-player SNES game represents a lot of technical initiative

The one thing that was almost a problem- it is borderline on the "turn based games disguised as action games" genre. 
You know. Practically very MMORPG does this. The combat works like: you and the enemy can both be freely positioned in the world, and can attach each other, but the attacks always land regardless of how you are positioned. Why have the positioning mechanic at all, then? Why not just have a menu? If they shoot an arrow or something it's not like you can move out of the way. I know why they do it in MMOs, but I'm less on board in any locally-played action game.
I suppose this bothers me because it encourages you to waste brain cells in combat trying to move around the map when you might as well just stand there.
Fortunately, this game doesn't 100% do that, it's only for certain attacks. Some experimenting helped figure this out. For other ones, you can move out of the way, sometimes outside of a hitbox that seems rather big.

On a whole I loved playing this game, and getting the chance to play it co-operatively even though it's long after the fact.