I wouldn't feel so bad for sleeping on TROR, perhaps it's my mistake for sticking to my DOS Duke 3D/Build roots but I still see it as a relative novelty, done right it can really enhance Build mapping but that's a step I have yet to take myself and a lot of other active mappers actually, you might be surprised by how much it really isn't a staple. I've been meaning to find the time to learn it for a minute now, mainly so that I can take part in this:
https://forums.duke4...or-cbp-rpoject/ which may interest you by the way if you've missed it.
I'm just glad to see more people approaching Build mapping on a bigger scale than they traditionally would these days, there is something about composing a large open landscape in sandbox type of settings that's a refreshing kind of enjoyable vs. micromanaging tiny detail and individual rooms and corridors where player movement is mostly constricted, when it's actually so good (and fast) in Build games and just waiting for the next opportunity to be exploited. The vertical axis is also one that is (or used to be) commonly slept on, so mountains always look fresh, I do feel like sometimes though it's also good to break down the monotony in the terrain and not make it all so consistent so that you also have abrupt vertical cliffs and some platforming in addition to the otherwise smooth looks, forcing the player to use the jump key on occasion and not just rely on slopes for elevation.
I'm putting some thought into this because I think judging from what you've shown, you already have the basis to make a great full-length single player level with little effort left compared to what you've already thrown in, I think this style would deserve more than a showcase kind of boss map and could easily be turned into a more memorable experience even just gameplay-wise. I'm not sure how many resources this piece of terrain is consuming already, but that's a whole batch you could easily clone and flip and reassemble ad infinitum (theoretically) to expand the terrain even further (but I wouldn't really recommend that - there seems to be a persisting limit to how much ground Build maps can have on display without generating visual errors and sector glitches), or copy-paste and turn into an alternate dimension or version of the same area to then use ROR tricks on really easily, or maybe you could add some breaks and gaps and play with sector elevation in bulk here and there to turn certain areas into separate (floating?) islands; or without even recycling anything, just adding a few key locations to the layout (that would especially be visible and recognizable from distance, I'd recommend using unique palettes) that the player would have to visit in order to trigger the boss fight should be easy enough to implement as well. Anyhow I just feel like your map in its current state could be repurposed in many interesting ways and it may be interesting to consider it a template of sorts; I could easily see someone make a whole episode out of derivations of this existing design.
Also, the reason why I'm pressing the 'sector grid' technique that much is I really believe approaching level design with coordinates and easily manipulable bulks of sectors (instead of intricate micro design) like that really has the potential to be the next step in Build mapping, it just makes the process so much easier in many aspects. My tutorial only goes that far in-depth, myself I was just figuring out its perks as I was writing it and now months later I'm still realizing new ones. Originally I found out about its usefulness when copy-pasting and assembling a bunch of square water sectors to form a big ocean around a level instead of drawing one huge sector that would most likely generate problems within the map (Build doesn't handle those well). Spontaneously I started expanding that habit to terrain design and including all kinds of patterns within the copied sectors and now mapping for me has basically turned into designing then assembling jigsaws, that combined with all the bulk manipulation tools and various shortcuts Mapster32 now offers has been enough to shrink my average time spent on designing one Duke 3D level from roughly three months to roughly two weeks. Basically I think for efficiency it's always good to remember that whatever it is you design also becomes a potential resource to recycle and repurpose and expand on, and I feel like the way you construct terrain would lend itself to such use very easily.
Following the same logic, I think there's a Mapster32 script or command that basically turns your level upside down too, like it inverts all the Z coordinates and attributes (not too sure there as I never used it myself). Apply that to your design here and boom you have the skeleton for a jungle- or cave-themed level, just add tree trunks and walls for structure. Or you could have both versions of the design as ROR connected with silent teleporters or over/underwater (the structure would already be in place), or just imagine the same irregularities (maybe with different values) on both the ground and ceiling, perhaps with some sections parallaxed, some not. Just trying to highlight how it's a rather precious structure you've got there, tons of possibilities you've (quite literally) laid out the groundwork for for yourself.
Help
Duke4.net
DNF #1
Duke 3D #1
still GG for your island !
