#PACKRAT GAME RUNNING SLOWLY PLUS#
#PACKRAT GAME RUNNING SLOWLY SERIES#

unseen territoryĪnd then you'd add on a layer of piloting skills to this. Fear of the unknown (bias towards moving through seen vs.Preferred engagement range (can be hard-overridden by 'Mech, so an long-range preferring pilot doesn't put his SRM boat at 600m).Jumpjet preference (heat, evasion, less accuracy, better visibility when jumping).Tolerance of and willingness to overheat.Preferred target type (infantry, armor, enemy mechs).Called Shot - risk higher miss % in exchange for focusing components.

Risk-taking behaviors (risk/reward calcs being based 2/3 on pilot and 1/3 on Mech settings).

#PACKRAT GAME RUNNING SLOWLY PLUS#

Similar settings to the above, plus additional ones covering: This would need to change with each specifically outfitted 'Mech, as a SRM boat Archer and LRM boat archer are going to require different settings. Weapon prioritization - if the mech can't fire all in-range weapons due to heat, which ones do you want it to fire first?.Weapon hit % threshholds (don't fire the 8-rounds-of-ammo Gauss until you have a 70% hit chance).risk overall (how much firepower and retreating are you willing to see versus risking damage to your few precious DHS?) Back armor risk (how big of a threat is this).Optimum/preferred engagement range (very close for Firestarter, very far for Awesome, etc.).I think making this work would require a larger number of sliders each pilot gets a set of sliders/characteristics, and so does each 'Mech configuration. In GSB, you set up your giant space fleet loaded with all sorts of science fiction weapons and shields, you place them in the deployment area, and you adjust some sliders to dictate their behavior (when to retreat, that fighters should target cruisers, cruisers should target cruisers, and frigates should target fighters, that fighters should return to re-arm and get fixed at 40%hp, what range to engage at, etc.) - and then you sit back and watch the battle, since you can't modify orders once the fight starts.

The approach I would suggest is to take a page from a game called Gratuitous Space Battles. With direct human control removed, that's a lot to consider. Does it go left or right? Does it have intel on enemies that it might open its back up to when circling one way or the other? Does the Dragon target the less-damaged Vindicator hoping to disable the bigger threat? Or does he focus fire on the Vindi that's missing its left arm and has a damaged left torso, hoping to destroy it first? If it circles too widely, then it takes too long. However, if it goes too close to the Vindicators, one of them will simply run to intercept and punch it, and that's a big risk. The Cicada wants to get there fast so it can blow out some back armor. Meanwhile, a Cicada is trying to leave the woods and circle around to get behind the Vindicators. Imagine a simple scenario: A Dragon is moving back and forth in a wooded area trying to be a hard target for the two Vindicators 300m away that are shooting at it. That is going to require a lot more programming going into the pilot AI and interface. When that happens, micro-managing every movement and weapon choice will not be possible. I think that's going to require some form of real time combat, probably Real-Time With Pause (RTWP). However, to enable bigger, larger combats and reach a larger audience in an eventual BT2 (2024-2027 timeline), the pace of combat is going to have to speed up a lot. where in MechCommander, you just point your mechs at an enemy and tell them to try to engage at short, medium, or long range - and that's it. Much of the need for this is driven by the granularity in HBS-BT: There are weapons to select/de-select, multi-targeting, coolant flushes, sensor locks, etc. If each battle produces an equal amount of Fun, then a game that produces Fun more time-efficiently creates more Fun overall.

#PACKRAT GAME RUNNING SLOWLY SERIES#

In other games, this 15 minutes is time for a whole bunch of combats in League of Legends, 1-2 12v12 drops in MWO complete with 1-2 minutes of walking towards the enemy, or an entire series of combats (with more participants) in MechCommander and, IIRC, MechCommander 2. A simple 4v8 mission takes upwards of 15 minutes to complete in most cases, simply because each 'Mech takes 3-10 seconds to move, aim, select weapons, target, fire, animate, etc.

My most frequent complaint about HBS-BT has been the overall game speed.

Packrat game running slowly