Leaderboard

Suggested here.

I'm not providing example maps because you won't be able to examine *.darkradiant as the maps are edited according to the steps below. After step 6, bring up a text editor and look at what DR has done with *.darkradiant. It looks like, at step 7, orville.darkradiant retains the layers defined in archie.map (good), but when you rename them in steps 8 and 10, and save the map, a new Layers section gets added to orville.darkradiant, rather than having the current Layers definition replace the previous Layers section inherited from archie.map (bad). I.e. it ends up looking like this: Layers { Layer 0 { Default } Layer 1 { Archie } Layer 2 { Walter } } Layers { Layer 0 { Default } Layer 1 { Orville } Layer 2 { Robert } } Layers { Layer 0 { Default } } 1. Create a new map. 2. Add an AI named Archie. 3. Add an AI named Walter. 4. Create layers "Archie" and "Walter". 5. Move Archie and Walter to their respective layers. 6. Save the map as archie.map. 7. Save the map as orville.map. 8. Change the "Archie" layer to "Orville". 9. Rename Archie to Orville and move him to the "Orville" layer. 10. Change the "Walter" layer to "Robert". 11. Rename Walter to Robert and move him to the "Robert" layer. 12. Save orville.map. 13. Open the previous map archie.map. 14. Look at the layers. They're Archie and Walter, as they should be. 15. Open the previous map orville.map. 16. Look at the layers. They're Archie and Walter, but they should be Orville and Robert. orville.darkradiant looks like the lines in the highlighted section above. It looks like there's some integrity problem with saving/recalling layers. I can't say when this first showed up, but I never saw this prior to this round of beta versions. I also had a situation where, when I was switching maps, the layers changed to those of a map unrelated to what I was working on. Since this appears to have been going on for a while, and I've been editing several different WIPs over the past week or so, I now have to unravel my layer settings. If I'm right about previous Layer definitions not being replaced, this might be as simple as removing everything prior to the latest definition. If somehow they've become tangled, it's going to be like unraveling a plate of spaghetti. So I'm stopping work until this is understood (and fixed). If this is a bug (and I'm not just seeing things), it will have affected any mappers using layers, for as far back as when the bug was introduced.

Something like that, recalling vaguely

Using Beta 4. I thought this HOM problem was fixed. View is from the eastern void in "Accountant 1".

Yes, i loved Thievery UT (never played nightblade) the unreal map I retextured, is still after 17 years there on that site

Hey, thank you very much for playing! Glad you liked it

Hey @krrg! Thanks for playing! Yeah, I realize I definitely did some unique things in this FM that might be a little weird at first, especially when , but I'd like to think it came out pretty well. As far as the secret goes:

Whoa, that is really weird. I don't have the slightest clue as to what could be causing that. Are you playing 2.07 or 2.08?? And yeah, not sure why peeking works for some and not others but I attached a picture of what it looks like. Pretty useful for spotting guards on the other side. And as far as the secret goes...

Thank you for the kind words Tarhiel! It is my first mission, but this was made on the back of several authors before me and hundreds upon hundreds of hours building maps, scrapping maps, learning things, relearning things, making mistakes, haha. This has been a long time coming. But I'm glad you enjoyed it! And I definitely plan on continuing this story as well