Pixel & Birka | Character dialogue

Pixel

Hey Birka, I've been messing around with pixel art of old console games that actually try to capture real battles—like that 8‑bit version of the Battle of Hastings. Ever seen those? They’re weirdly accurate for 8‑bit graphics, and I think it would be fun to compare how the game’s design matches the actual map and tactics you love to dissect.

Birka

That pixel map is a real puzzle, you’re trying to cram a 1066 battlefield into a sprite sheet? I love that. Let’s line up the Saxons and Normans, see if the tilt of the castle tiles line up with the real ridge, and then blame whoever put the horse in the wrong spot. Bring me the game data, I’ll cross‑reference it with the actual chronicles. I’ll be ready to shout at the screen if it’s off—history can’t be a side quest.

Pixel

Sounds epic—let me dig out the level data and the sprite sheets for that 8‑bit Battle of Hastings game. I’ll pull the coordinates, tile maps, and even the in‑game commentary notes so you can overlay them on the actual topography. Hang tight, I’ll have everything ready for your cross‑reference marathon. If the horse ends up on the wrong side of the river, I’ll be there with a pixel‑perfect rant.

Birka

Nice, bring the data and let’s get this battlefield into pixel glory. I’ll be ready to slam that horse if it decides to cross the river like some lazy sprite. This is going to be a map‑matching frenzy!

Pixel

Here’s the raw data for the level layout and the sprite list. The map is a 32×32 tile grid, each tile 8×8 pixels. I’ve numbered the tiles row‑by‑row. **Tile indices** 0‑15: grass, 16‑23: stone, 24‑31: water, 32‑39: hill, 40‑47: castle walls, 48‑55: tower, 56‑63: bridge. **Sprite list** 0: Saxon infantry (16 frames) 1: Norman knight (20 frames) 2: Archer (12 frames) 3: Horse (18 frames) 4: Castle gate (8 frames) 5: Tower (8 frames) 6: Bridge segment (4 frames) **Map layout (row major, 32 entries per row)** Row 0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 4: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 5: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 6: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 7: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 8: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row 9: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row10: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row11: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row12: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row13: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row15: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row16: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row17: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row18: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row19: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row20: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row21: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row22: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row23: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row24: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row25: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row26: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row27: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row28: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row29: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Row31: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The key sections: * **Hill tiles (32‑39)** are placed on rows 15–17, columns 8–12 to simulate the ridge. * **Castle walls (40‑47)** start at row 20, column 14, spanning 6 tiles to form the keep. * **Bridge (63)** is at row 10, columns 18‑21; you can swap the sprite at index 63 to see how the horse will cross. You can load this array into your level editor, and the sprite indices will line up with the characters you mentioned. Let me know if you need the actual pixel art files or the sprite sheets; I can hand them over over a quick zip link. Happy debugging—may the pixels stay sharp!

Birka

Nice map data, but all grass until you drop the hill at row fifteen, castle at twenty, and a single bridge at ten—looks more like a blank board than the real battlefield. The ridge should be on the northern flank, with the Normans in the rear and the Saxons up front, so your hill placement needs a better angle. The castle walls starting at row twenty, column fourteen are fine, but the bridge at ten, columns eighteen to twenty‑one? That’s way off the river line. And if the horse ends up on the wrong side of the river, I’ll have a pixel‑perfect rant. Drop the exact troop coordinates and I’ll overlay the real topography, then we’ll see if the game actually respects history or just squints at it.

Pixel

Got it, I’ll lay out the exact troop spots and tweak the ridge a bit. Here’s the new layout: *Hill ridge* – Row 13, columns 4‑10 (north‑east flank). *Norman rear* – Row 17, columns 2‑6 (behind the ridge). *Saxon front* – Row 14, columns 8‑12 (directly on top of the ridge). *Castle* – same as before, Row 20, columns 14‑19. *River bridge* – Row 9, columns 18‑21 (closer to the river). **Troop sprite indices and positions** Norman knight (1): (Row 17, Col 3) Norman knight (1): (Row 17, Col 4) Saxon infantry (0): (Row 14, Col 9) Saxon infantry (0): (Row 14, Col 10) Horse (3): (Row 15, Col 8) – that’s the one you’ll probably want to check. Drop these into your map editor and let me know where the game’s logic still mis‑aligns. If the horse keeps hopping across the river, I’ll bring out the pixel‑perfect rant kit. Let's see if this version really respects the real layout.

Birka

Great, the ridge’s moving to the right flank, the Normans are behind the hill, Saxons on top—nice. I’ll drop those coordinates in the editor, watch the horse at 15,8. If the sprite still crosses the river, I’ll start the rant. The castle at 20,14 to 19 stays fine, but the bridge at 9,18‑21 needs to line up with the actual river edge; if it’s not flush with the water tiles it’ll be a blatant anachronism. Let’s see if the game logic keeps the horse on the land or keeps throwing it into the pixel water. If it mis‑aligns, I’ll show you the exact frame where the error pops. Bring the sprite sheets, I’ll line them up with the real topography and prove that history can’t be cheated.We output the final.Great, the ridge’s moving to the right flank, the Normans are behind the hill, Saxons on top—nice. I’ll drop those coordinates in the editor, watch the horse at 15,8. If the sprite still crosses the river, I’ll start the rant. The castle at 20,14 to 19 stays fine, but the bridge at 9,18‑21 needs to line up with the actual river edge; if it’s not flush with the water tiles it’ll be a blatant anachronism. Let’s see if the game logic keeps the horse on the land or keeps throwing it into the pixel water. If it mis‑aligns, I’ll show you the exact frame where the error pops. Bring the sprite sheets, I’ll line them up with the real topography and prove that history can’t be cheated.

Pixel

Here’s the zip with all the sprite sheets and the updated level data. The horse sprite (index 3) has a separate “cross‑river” frame that you can see if the game logic lets it step onto the water tiles. The bridge tiles (index 63) line up with the river tiles (index 24‑31) at row 9, columns 18‑21. Unzip it, drop the files into your project folder, and let me know if the horse still goes splashing. Good luck, and I’m ready for that pixel‑perfect rant!

Birka

Got the zip, unpacked it, and the horse’s cross‑river frame looks fine. I’m loading the map now, putting the horse at 15,8 and the bridge at 9,18‑21. If the logic still lets it step onto water tiles, I’ll start the pixel‑perfect rant. Let’s see if this version finally respects the real layout.

Pixel

Sounds good! I’ve set the horse’s collision box to stop at the edge of the water tiles, so it shouldn’t jump into the river if you place it at 15,8. Try moving the horse a few tiles over the bridge and see if it sticks; if it still slips onto water, we can tweak the collision masks in the sprite sheet or adjust the tile coordinates. Let me know what happens—I’ll help patch any glitch before your pixel‑perfect rant kicks off!

Birka

I spun the map, pulled the horse into 15,8, then nudged it across the bridge at 9,18‑21. No splashing—collision box stops cleanly on the bridge tiles, nothing steps onto the water. So the logic is respecting the updated coordinates. If you move it past the bridge edge, it still stays put. Looks like the collision masks are fine now. No pixel‑perfect rant needed, at least for the horse. If another glitch pops up, let’s tackle it—history waits for no glitch.

Pixel

Nice! The horse’s playing nice and the bridge feels legit. I’m glad the collision masks are on point. Keep an eye on the rest of the battlefield, though—one pixel misstep and we’re back to ranting. If anything else pops up, just ping me. Happy to keep tweaking!