-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework some levels / map packs #8
Comments
I really would love to make a new set of levels for the new release and rename the old default mappack "old" or something like that. You know, to take advantage of the new features that'll be added. Bwahahaha! |
Actually, I don't think there is a need for a complete change of the default levels. I might have been a bit rude, but there obviously are some positive points: there is a logical progression (no boulders at first, etc). So we could just insert some levels with the new features alongside the "old" ones. But we're not there yet, the expected "new features" still need to be implemented :) |
"radad's challenge" has a priority of 8, while any other map pack (expected for the official ones) have a priority of 5. Is this intended? The result is that there's a map pack of difficulty "impossible" amongst the very first map packs in the list :) |
The priorities aren't really thought out. I didn't know if the lower numbers belonged on top or bottom. So I just left it. But when that's done I think we can close this. |
Feel free to close the ticket whenever you feel like it's ok ;) The standard priority for map packs is 5. Higher priority should be used with care, as priority takes precedence over difficulty (map packs with equal priority are sorted by growing difficulty) I believe we should use something like 10 for the two official map packs, so that they show up first. Then the same priority (5) for all other map packs. Maybe we could make the priority optional in infos.yaml (in which case it gets a default one like 5) |
The default levels are generally fine, although it sometimes lack explanations; also, some levels are really boring (no example right now, if you have some...)
In my opinion, the biggest issue is the first level. It really is disturbing to own a portal gun while not being able to use it (there isn't any sticky wall). Also, the way doors work is a bit confusing at first.
For the first issue, we could implement something to actually prevent the player from owning the portal gun (e.g. a special command in the map file that gets interpreted at parsing time). Or we could just allow the user to play with the portal gun starting from the first level, although it isn't the case in the real Portal (iirc).
It might be wise to split the default levels into two different packages. I believe 50 levels is a bit too much, there's always a risk of being bored or stuck (what do you think?). This is especially true because of the brand new moving platforms that are likely to bring even more levels to the default pack.
As for non-official (although that's hard to define properly ;) ) map packs: while some are really nice and well-organized (I especially like ratpack and its continuous levels :) ), some others still need work.
The text was updated successfully, but these errors were encountered: