>>6020639
Do not do any sort of random generation in regards to levels. Making a really shitty procedural generation of levels is easy. But it will be really shit.
Making procedure generation of a 3D level that is least decent is incredibly hard, and requires a dedicated team.
Handcrafted levels is the way to go.
If you are going for low-res - always consider intended internal resolution of your game, and palette from design standpoint.
Main mistake of te indies is mixing assets of different detail density, using diferent palette limitations for different things, using lower resolution assets than the games of the period they try to mimix had actually used.
It's best to establish internal resolution and palette you are going to use at the start - same as Doom decided that 32 units/pixels is a meter, and every asset sticks to it - both sprites and textures.
You may chose a different metric, or make things more detailed, but you should keep it consistent. There are few things uglier than Commodore-tier spritework on Duke-era textures.
Dont mix styles and methods of asset creation. Rotoscoped sprites dont mix in with mspaint textures.
Do not use material effects (PBR) unless you REALLY know what you are doing, or you may end up with wood and earth textures that look like they are covered in slime (like Nightmare Reaper, or that terrible Doom PBR))
If you do want some PBR, look at how Duke World Tour did it. Use similar restraint, and if you do decide to use it, do not leave heightmap generation to automated scripts.