Well, the name of the folder itself doesn't actually matter - before the functionality of addon changed I used to develop all my maps and mods in the workshop folder, using subfolders that carried the name of the mod rather than a workshop ID.

What are the precise locations of the two versions of the map, and what does the .ini look like? Without that information, the only suggestion I can make would be to remove your test folder.

Thanks, good suggestion - removing the test folder appears to have done it. Initially, the files in the test folder were identical to the steam 'official' folder (except for date stamps) - I tried changing the mission name slightly in the .ini in the test folder, and then that showed in the map list, but the 'official' one didn't. Removing the test folder and having the 'official' one then show in the map list apparently indicates redux has/does some sort of file-check/comparison and if identical (content-wise) .ini's are in two different workshop folders, redux won't show either map in the map list. If the name or date of the workshop folder makes no difference, perhaps redux prioritizes which map it shows/uses based on the .ini time/date stamp as long as the .ini mission name is different but all other files between the two workshop folders are identical, aside from date stamps. Interesting, I wouldn't have thought it to be that discriminatory, and would just show in the map list any maps it finds in 301650 sub-folders, including duplicates. Maybe the conflict is as simple as not being able to resolve how to alphabetically list identical mission names... except, then, changing the mission name in one .ini should have both maps showing, so it would seem it's not solely an alphabetizing issue... hmmm.

Another question - what's the best place for created content uploaded to steam? Or is there a 'best' place? Sub-folders in workshop? Anyplace but addon? Redux automatically accesses anything in addon subfolders too, right? With the uploader's "update" function, obviously uploaded content should remain where it came from in the event anything needed updating, so following some consistent convention would seem a good practice, & created content needs to go someplace it won't create conflicts with the game's functioning - which I had happen before fiddling around with map porting and having custom odf's in addon that went with a map I was working on.

I had a feeling that might fix it. Battlezone will only read one a map into the mission list once.

The current release version of content uploaded to the Steam Workshop will exist in the /workshop/301650 folder, so that's the folder you should base your work on. Any incremental version that you're keeping around for version control or something would be best kept outside your installation directory.

With the release of the new patch I tend to use /addon as the working directory for developing mods that haven't been released yet and /workshop/301650 as the working directory for mods that have been released but that I am producing an update for.

If the uploader doesn't find map files in the folder from which they were originated for an update (due to them being moved or removed), does it give the option to select a new locale (and store that locale?) , or something else like crash or lockup/freeze unless map files were put back in place or back into a re-created folder named whatever it was when originally uploaded?

The process of updating a workshop item is very similar to that of uploading in the first place - it still asks you for the location and it still asks you for the thumbnail.

Yeah, don't think I've had to update anything - was thinking it might be more automated, check what files were different and upload those. Easy enough!