Bitfighter Forums

1. What if armor had a very limited immunity to asteroids? Just enough to not die on impact. Health would run out rapidly if contact with an asteroid was sustained. I don't know exactly what boosts have been added into 019 for armor, but this seems like a simple boost.

2. I just discovered the loadout preset menu... and while it is quite lovely, there's no way I'm going to remember which preset is which. Some suggestions for an upgrade:
- Have presets be nameable in the .ini file. Preset names should show up in-game right after you apply them, and perhaps contain a list of what's packaged within the preset.
- Merge the preset menu into the loadout selection menu. Just a simple hierarchy would be nice. Ex. Press Z once to access general loadout menu, then Z again to access preset menu, then # key to choose preset. Or keep the alt-1, alt-2 and put those on the same menu. Idea here is to give a complete list of all the presets you have installed.

3. While in commander's map view, have a player's ship flash briefly when they send a message. Would be helpful in scenarios where you're trying to call for help. Just saying help in chat is useless, even if someone has their commander's map open, since a player's location often cannot be easily deduced.

One difficulty worth noting, that I haven't really solved yet, is how to differentiate and/or signal when multiple people are chatting at once.

Also have any player who is carrying a flag on your team (in all modes except for nexus, for obvious reasons) glow slightly to signify their presence.

4. Add a zoom in function to the commander's map. Could be a simple as left clicking for in and right clicking for out. Or perhaps scroll. I don't think anyone actually tries to fire while in commander's view (or is successful, anyway). [But that is a subjective argument, so correct me if I'm wrong.]

Thanks! Can add these to the project page but figured they might require a little discussion first.

1. Already done for 019

2a. There is a [LoadoutPresets] section in the INI, even in 018a (I think)
2b. Interesting idea - a preset menu. I like your mechanism idea, too.

3. There's been discussion of a beacon or other notifier for the commander's map. I think I like the idea, but we'd have to work out the mechanism because the c-map is quite a bit different than what most games use.

4. A zoom function on the commander's map would only show walls, not moving objects (unless a teammate is in the area and giving you visibility). Also, this seems like it would good for dungeons, but maybe not for normal play as it is generally faster-paced. (But I concede I don't play as much as many of you do.)

I know, that's how I discovered it in the first place. Can the presets be given names, though? That's all I'm asking with this point.


That's true, although in addition to walls it'd reveal more precise movement of your teammates. It might not actually have as much use as I was thinking about. But I do think it'd be helpful for large maps and, daresay, dungeons.

https://code.google.com/p/bitfighter/issues/detail?id=285
https://code.google.com/p/bitfighter/issues/detail?id=295
https://code.google.com/p/bitfighter/issues/detail?id=296

I am unsure about the names -- I can see the advantage, but it would be good to be able to configure that sort of thing from in-game, and I am not sure how it would work.

It may become more obvious (or less necessary) after we implement the two cases above.

As for a zoom function in cmdrs map, it seems to add needless complexity, but perhaps we could have 3 map modes -- normal, cmdrs, and something in between that only shows what's on cmdrs screen, but at an intermediate scale.

Sweet, thanks for adding the cases.