Hi! Interesting screenshot ...

Can't you just put everything in the right place in the zip-file instead of writing annoying instructions, where to put what file? :)

Okay, here's a list of things I noticed about the map as I play(ed) it the first time:

Some of the asteroids rotating in the skybox have black outlines that should probably be removed or at least lessened.

The jumppad particle bars look cool. However, on the platform with the ship, it seems like the three ways to leave (2 jumps and a tunnel into the base) shouldn't all be clustered in 90 degrees of the circle. I think the jumppads should be moved further from the tunnel to use the space better. It would look more like the others then, which isn't great (more on that later) but it might lead to bad gameplay at that spot.

Having pickups double-stacked on each other is interesting.

In the center room, there is invisible geometry around where there should be a mapmodel, but I don't see any model. Is this something from Warzone pt. 2? (I have not downloaded it yet, but I had hoped that this map worked as a stand-alone)

The arches on the tunnels to the main body of the station look wierd because they don't appear circular, instead coming to an awkward point.

sometimes when taking the jumps, you bounce off the asteroids at odd angels and fall to you death, and it's mostly luck.

The main structure looks funky from below when you fall off. [ditto for getting on top of it, which is pretty easy, actually]

Why are there no capture bases in the middle of the map. It seems weird that there aren't.

---

The gameplay of this map is sort of lacking, because it's just the same flat platforms copy-pasted in four directions. I don't have much to say specifically, because it's just flat and sparse, and not significantly different from most of your other multiplayer maps. You won't hit you head anywhere or any other gameplay things people complain about, so good job with that I guess.
The lighting is nothing special, but it gets the job done. Pure white lighting is often frowned upon, but it works fine in shiny outerspace locations. However, it's weird that a planet is the lightsouce, as planets and moons only reflect light from stars, but whatever.
[random thought that I will probably never do [would require making a skybox]: A map in space where the lightsource is a sun BELOW the map. It would also be a good explanation to why you die if you fall off, and to why there would even be gravity pulling you down toward it]

Overall, 5/10 I guess

Content
I start to consider not to download your content anymore as the packaging keeps being horrifying. People (and I) keep mentioning you should package it differently, yet it seems like you're giving it your own twist.
As you probably are going to use more custom (map)models, skyboxes or even textures, I would advice you to put them in seperate folders like this:
Mapmodels: packages/models/mapmodels/pyccna/
Skyboxes: packages/skyboxes/pyccna/
Textures: packages/textures/pyccna/

Why I even suggest to do so? For several reasons:
- It is way easier for you to find back your content after a while within your very own Sauerbraten directory.
- It is easier for people which download the content to find all related content which requires the map back.
- It keeps the Sauerbraten directory less messy as it already is (even with the seperated MyGames directory, it turns out to be a mess after a while as people still just dump their stuff as quick as possible).

Why I won't suggest to use the name of the map?
- As you might want to use the content on another map also, which makes it look quite odd (and illogical) when downloading the latest map which runs with the elder packaging.
- As other people might like to use the content also. Why should they actually have to reference a map which isn't in their packaging? Let them rather reference to the guy who actually packaged the content.

The screenshot seems ok, nothing to say about that.
Where is actually the license of those skyboxes? There is only a quick reference to NASA but that's a pretty big organization.

Texturing
The texturing could be done better. It's quite plain. The planel2a texture of trak5 has been really overused (seems like there has been relied to much on the trimmings inside the texture). Using the light1a texture of trak5 on a wide spread area looks pretty odd.
Using graypanel3 of trak5 on the outside looks really weird and isn't fitting the geometry at all.
There hasn't been any textureblending as far as I could see, too bad; what a missed chance.

Geometry
I'm actually quite surprised that the map still consists out of 163k of wtr while a lot of models have been used. My best guess is the trimming which is on top of those long paths takes a lot of wtr (and is textured very choppy?).

Lighting
I've noticed you've set the mdlambient really high (it normally is 30, while you've set it to 125!), while you probably haven't played with mdlfullbright, neither with mdlglow (which only actually is effective when using a mask, but that's done very easy by specifying the skin once more).
The rest of the map has a pretty plain white lighting which feel quite boring.

Detailing
While I often advice mappers to use more models, I would rather advice the opposite this time; use less models. Those asteroids don't need to be models, neither those barricades (why are they on the map anyways?).
The asteroids use way too much vertices than necessary and it seems like you haven't used remip before exporting them?
Using those capturemeter-particles as lighting or notification of a jumppad is quite original, but too bad; they are rendered 2D. This makes them appear quite odd in a lot of angles (except when you appear from front of course, but that barely happens).

Clipping
Clipping seems one of the best things on the map, not much to say about that.

Flow
The flow of the map; well there actually is barely. All platforms are on the same height (with 1 top layer on the paths which lead towards the platforms, not a big hit either), while some small barricade is the only thing which provides a little cover on the gigantic areas.
It's better to set the jumppads with a strengh that you actually have to push the forward button also to get there, as players tend to press that button 24/7 anyway. It would make it feel odd if you suddenly have to release the forward button to get to a specific area. Of course, you should keep it quite loose so players won't die due lagging or just let the forward button slip.
You've ever checked out the map called asteroids? I would advice you to do so as that map provides nearly everything which this map tend to lack.

Gameplay
I'm not font of concentrating pickups that close to each other on such wide open map. That just asks for trouble when someone tries to pick any weapons or health up.
Seems like you've added enough playerstarts, good job on that. Still quite odd that you've placed playerstarts facing the other direction as a jumppad goes (to the centre of a platform) as another player could just take a ride from a jumppad on the asteroid while you spawned, which means a cheap kill for the opponent while you die once more.

Overall
You should pay more attention to your layout, spend more time on just 1 project and look around on maps which have already been released. Don't try to invent the wheel another time, invent a way to make it roll better.
I'll rate it 4/10 for now.

Fixed it again (if this packaging isn't correct, then there's no 'correct' way), added more catwalks between platforms and several other mapmodels for cover and ambiance, updated the Vampyres to the new Vampyre MKII, changed the health-to-weapons ratio layout, edited the skybox so the sun looks like a sun, made the central asteroid climbable with quaddamage on it (added a base there too), made the 4 asteroids have 2 more pathways and moved the healthboosts, and the map is now CTF compatible for another test-drive of the pseudo-class system.
P.S, before the mapmodels, this map was 450k (the asteroids and towers took up most of that), now it's 158k.

До свидания и Спасибо
-P