lowtech VS gbt-player

On old computers, you could go even faster by precomputing tiles representing little segments at various angles and then copying tiles. The trick here is to realize that you don't need many tiles to represent all the lines. The downside is that it's not quite accurate. But it's much faster. See an example here :

https://github.com/wiz21b/lowtech#the-3d

Very cool. But it's also a good answer to the GP and some of the downthread colour questions - if push comes to shove, you can just ignore the colour. You didn't link it so I'll take the liberty: github repo is at

https://github.com/wiz21b/lowtech

This video (plus the next part in the playlist) has an intro to creating music using GBDK and GBT Player https://www.youtube.com/watch?v=7l93RP986Zo I gather that hUGEtracker and hUGEdriver https://github.com/SuperDisk/hUGEDriver are the new preferred music tools with GBT player https://github.com/AntonioND/gbt-player being an older, more complex option (I haven't used them enough to form an opinion).

I want the .mod file (or some equivalent transcription of the notes/instruments that I could import or convert) so that it will work with GBT Player. I'm doing a project which uses GBT Player to play the music.

If you're asking how I made the game itself, I wrote it from scratch in GBz80 Assembly. I'm using RGBDS for assembly. Most of the assets are converted to a usable format with custom Python scripts. The music is made with OpenMPT and converted/played with gbt-player. The map tool in the video is a collection of C# scripts that generate and export assembly by parsing the Unity scene. Here's what the file looks like.