Destroy the Godmodder: MSPAradox (Test Session)

New Charging and Entity Rules:

Thanks to the Simumodder taking its first point of damage, active charging and entity summoning has been enabled! A copy of these rules will be posted in the OP.

Charging Mechanics:

In addition to spending actions on Battlefield actions, you can also convert actions into Charge Points (or CP, for short) that can be stored in an active charge. An active charge represents an immediate Battlefield action that is difficult to counter and has a power equivalent to multiple individual actions (e.g., a charged attack, a charged heal, a charged assist, etc.) and requires the expenditure of CP. An active charge can also be expended to summon entities onto the Battlefield (entity summoning is explained in a later section of the rules).

Players can trade each other CP as a free action. However, attempting to combine multiple active charges together may require a multi-turn combination sequence to function (especially if the combined charge would be particularly strong), and the participating players and the “ritual” must be defended from enemies.

Entity Mechanics:

Entities are the NPC combatants of the Battlefield who serve the players or Simumodder directly. In addition to bodyguarding combatants, entities make the opposing team’s combatants more vulnerable, and serving as the target of most attacks. Each entity acts during the End of Turn Battle (or EoTB, for short), in a set order (usually it’s AG, Neutral, PG, and finally, the Simumodder). Summoned entities can be whatever the summoner desires: characters from pop culture, original creations, you name it! Regardless of origin, entities are defined by their stats and mechanics: HP, attack, Dodge, Armor, etc. The summoner is free to design their entities with whatever mechanics they wish, as long as they are balanced according to the power of the action or charge used to summon them. In general, entities are balanced by investing actions or CP into their stats - if you’re trying to summon a tanky 10-charge entity, you might give it 8 CP worth of health or defensive abilities and 2 CP worth of attack and offensive abilities, while a glass cannon might receive 3 CP worth of health or defensive abilities and 7 CP worth of attack or offensive abilities. More detailed notes on balancing specific stats are below, in the List of Useful Entity Stats and Mechanics. Putting more CP (passive or active) into an entity will make it stronger.

List of Useful Entity Mechanics:

While none of these stats are strictly required in an entity, they are still very useful and easily applicable.

Show Content

Spoiler

• HP: This is probably the most common stat that an entity has. While some entities can have their own equivalent stat that tracks how far away from defeat they are, most measure theirs with HP. HP scales according to player power - each action or CP equivalent invested into HP is equivalent to twice the average attack of a player with standard-level alchemies.
  
• Attack(s): Generally a single statistic for simple entities, but you can give entities a variety of special abilities. Each, however, is balanced around an entity’s “average attack,” with each action or CP equivalent invested into average attack translating into 1/2 of the average attack of a player with standard-level alchemies. Inflicting status effects or using gimmicks such as AoE will deduct attack power from an ability or attack. If you want an entity to have expensive but powerful attacks or abilities, a good way is to give those attacks a cooldown, which multiplies the power of that ability.
  
• Dodge: This is the ability of an entity to avoid attacks directed against them, and is treated as a functional HP boost. In general, the probability to hit an entity is Accuracy of attacker - Dodge of defender. A unique variant of Dodge is Parry, which only works against melee attacks but is more effective against them.
  
• Accuracy: This is the ability of an entity to target hard-to-hit entities or weak points in an entity. The average entity Accuracy is 100% - entities with less than 100% Accuracy may not be able to consistently hit even non-dodging entities, while entities with more than 100% are not only able to hit dodging entities, but can also minicrit or outright crit on their attacks. Because of this, Accuracy is treated as an effective damage boost or penalty.
  
• Armor: As a separate stat (instead of just an entity component), Armor acts as a flat damage reduction that is counted as a functional HP increase for balancing purposes. Specifically, Armor adds a CP cost multiplier (or HP reducer) equivalent to (1 + (Armor value/average player attack power)). However, some player attacks and items, in addition to entities with Armor-Piercing attacks, will be able to partially or fully ignore the Armor value of an entity.
  
• Critical hits: In general, an entity minicrits if it rolls a value of greater than 100 on its hit chance roll, while an entity crits if it rolls a value of greater than 125 on its hit chance roll. This is only possible if the entity has an Accuracy higher than 100%, or if its target somehow has a negative Dodge rate. You can also put in Critical Chance as a unique entity mechanic. In both cases, crit chance is treated as a functional damage boost for balancing purposes.
  
• Range: Range is a numerical value which indicates the distance at which an entity can engage an enemy. An entity without Range is classified as a Melee entity, which means that it cannot engage enemies in distant areas or enemies outside of its Domain except under special circumstances. Adding Range onto an entity allows it to attack enemies in areas with a distance equivalent to its Range score, with Aerial enemies requiring one extra point of Range to attack. Each point of Range costs (total CP or action cost of entity/10), rounded up.
  
• Domain: This is the region in which an entity operates. An entity can either be Grounded or Aerial. An entity can also be granted the ability to transition between two domains at the cost of a CP. An Aerial Melee entity can attack Grounded entities, but doing so will allow Grounded Melee entities to attack the Aerial entity on their turn.
  
• Healing: Instead of being purely offensive, you can give your entities abilities that let them heal other entities. In this case, healing is treated as attack for balance purposes.
  
• AoE: Area of Effect attacks or abilities can affect multiple entities at once. Unless the target has a specific counter to it, AoE attacks can also ignore a certain amount of Dodge, with the specific negation equal to (AoE attack power/1,000).
  
• Armor-Piercing: Attacks with Armor-Piercing are able to ignore Armor up to the numerical value of Armor-Piercing. For balance purposes, Armor-Piercing is treated as 25% of a damage boost, as many entities do not have Armor.
  
• Horde: Horde entities are entities that are composed of many attackers instead of just one and a few components. The standard rules for entities apply differently to Horde entities - Hordes do not have Dodge or Armor stats, as those would be redundant or overcomplicate Horde entity combat. As a Horde’s attack represents many small attacks, an enemy’s Dodge rate is treated as a pure damage reducer (the Horde’s damage is multiplied by (1 - Dodge), to be specific), and a Horde’s accuracy is treated as a damage multiplier. In addition, a Horde’s attack power and Armor-Piercing stat decreases as the Horde takes damage. To compensate, a Horde starts off with increased stats.
  
• Power system: Another way to balance an entity is to make its abilities cost “power” to use, which strengthens them at the cost of adding resource management into the gameplay mix. There really isn’t a set template for power systems - so feel free to design one however you like, as long as it remains balanced.