MegaMek / mekhq

MekHQ is a java helper program for the MegaMek game that allows users to load a list of entities from an XML file, perform repairs and customizations, and then save the new entities to another XML file that can be loaded into MegaMek.
http://megamek.org
131 stars 168 forks source link

Stratcon Roadmap #2649

Open NickAragua opened 3 years ago

NickAragua commented 3 years ago

This is a short and poorly-explained list of features I'd like to implement for StratCon, in no particular order, more as a memory aid than anything else. Subject to change on a whim or if something gets to be too difficult/invasive to code.

-[X] "Player/Attached" unit generation (generate X units; player may deploy units of the same type to replace them) for scenario templates --[X] Modify "Defend Grounded Dropship", "Low Atmo - Escort", "Space - Blockade Run" scenarios to use new unit gen method for the dropships [] Create "Hot Drop" modifier with new unit generation method [] Create "Landing Zone Defense" "facility"scenario - similar to allied base of operations, but it's your dropships and all your stuff.

[] Finish facilities: [] Supply depot: +1 SP per week (allied) / something bad (hostile) [] Data center: reveal map (allied) ? / something bad (hostile) [] Early warning system: ? [] Orbital defense: (original concept: prevent opposing aerospace activity in area)

[] Create "Strategic Asset Defense/Assault" space scenario. The concept is to have a jumpship/space station/warship that needs to be defended/destroyed. Perhaps limit it to fixed scenario objectives, as it's quite difficult to balance, especially with warships.

[] Hostile units that you don't destroy, especially from scenarios you ignore or lose, go into a reinforcement pool. [] Fixed facility garrisons [] Fixed facility maps

[] Introduce more contract types from CamOps (mole hunting, terrorism, etc)

-[X] Terrain/biomes on tracks on strategic map (influences available terrain types and weather conditions for scenarios appearing on hex) --[X] random track terrain generation should depend on planetary equatorial temp --[] water coverage

[] Usage of "pre-built" maps instead of randomly generated maps when pre-built map is of the appropriate size

MegaMek features: [x] Bot minefield avoidance [] Pre-battle terrain modification by players ("place X buildings of CF Y, Type Z on some/all terrain types", "turn all light woods to depth 1 water") - allow definition of such in scenario templates [] Carryable objects - allow definition and placement of such in scenario templates for objective purposes [] Detachable jump packs

Tecmes commented 3 years ago
rroby1 commented 3 years ago

Revealing the map for data center is good. What about adding intelligence, i.e. number of enemy units, types, etc. The numbers & types are estimates of course. Something like 3-6 mediums, 6-9 lights, etc. As you deploy scouts and conduct recon those numbers get better. On the bad side those numbers are way wrong.

Windchild292 commented 3 years ago

@NickAragua To fix the list you'll need to do - [ ] or - [x], not [] or [x]