Jump to content

JediRP Staff

Administrators
  • Content Count

    10
  • Joined

  • Last visited

    Never

Community Reputation

0 Neutral

About JediRP Staff

  • Rank
    Padawan

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Alias Rules Players should avoid when possible exclusively interacting between their own aliases during peacetime. We understand that sometimes circumstances will make a player have to have multiple aliases in say the same meeting, but in regards to one on one interactions avoid self interaction as much as possible. The element of chaos that other players bring is important in making your character grow in unexpected ways, and player connections help build a more compelling universe. During fleet battles, each player chooses a side to determine task forces. Regardless of the number of aliases a player has, they are only counted once for the purpose of fleet command. Players can bring any number of aliases for PvP duels, but each participating player must have a duel lined up before players with multiple aliases can start to stack additional duels with other already engaged players. Players cannot duel themselves. If a player has reached knight/lord or equivalent status in a faction, subsequent aliases they make can skip the apprentice rank and start at knight/lord or equivalent status, or they can choose to self train rather than seeking a PC master. If the player makes this new character while they have another character still in the faction or are cycling from a prior character within the last three months, the new character must use one of these two options unless they have express consent from a master. This is to give new players priority for training and prevent training burnout. It is highly recommended that players that have been absent from the RP for a period exceeding two years start with a fresh alias on account of shifting power levels and board meta changes. Players can only hold one leadership position at any given time in the factions, regardless of the number of aliases they possess or the standing of those aliases within the factions. We want to make sure that older players, who tend to have both the connections and aliases to secure multiple positions don’t unintentionally gate off political advancement for other players in a faction, or have to compartmentalize their player knowledge due to holding commands in opposing factions. While we have relaxed rules on using multiple aliases, we would like to add that using multiple aliases in tandem to achieve your goals through unnatural cooperation is frowned upon and subject to mod review.
  2. Task Forces, Wave One (all of these are task forces, names are for flavor) Battleline Escort (A Capital ship): Tradition of excellence Green: The TF regains two points of shield damage at the end of each round. Veteran: The battle line can focus all power to shields and halve(rounding up) the power of any direct removal abilities (except for artillery) for the round. While this ability is in play, abilities that would normally bypass shields from TFs like the Hellriders and Covert Strike Force hit the shields instead. While this ability is in play, the TF takes double damage from artillery attacks, and enemy ships do not suffer penalties from combining fire on the ship (although the three TF cap for combined attacks remains). Elite: If the fleet is in danger of total destruction, the task force can launch a suicidal assault to allow all other allied ships to flee the battle. Doing this wipes out the battleline TF, but it can prevent a wipe by an interdictor supported enemy fleet. Additionally, the TF can reduce one source of removal damage to one damage once per battle. Interdiction cadre (Interdictor cruiser supported by frigates and corvettes): Interdiction field Green: Gravity wells severely hamper retreat, forcing the enemy to only withdraw half their fleet each turn. Veteran: Interdiction fields can be used to precision deploy fleet assets, but this damages their hyperdrives, preventing them from being able to withdraw early for the rest of the battle. Elite: As long as the interdictor is functional, its crew can largely prevent any ships from fleeing. Enemies can only withdraw one task force each turn. Precision Strike Carrier Group (Capital or cruiser supported by frigates and corvettes): Fighter Command Green: The TF controller can perform an additional starfighter action for the round, that must be Bombers Inbound. Veteran: Bombers Inbound does an additional point of damage. Elite: The TF controller can perform an additional starfighter action for the round, that must be Fighter Escort. Electronic Warfare Pod (Dedicated EW and comms cruiser with frigate and corvette support): Information Control Green: The TF can jam long range communications and sensors. Veteran: The TF can perform an additional scan on any allied TF to search for concealed enemies. Elite: The enemy penalty for targeting the same task force with more than one task force becomes a cumulative -3 instead of -2. Defensive Escort (Frigates and Corvettes): Suppressing Fire Green: An allied task force that is adjacent to the task force is treated as if being supported by interceptors (The defensive escort can select itself) and starfighter actions on protected ships are resolved at delayed speed. Veteran: The TF can cover an adjacent task force and itself in the same turn, and corvettes lose their defense bonuses tied to maneuvering and speed when engaging or being engaged by covered assets. Elite: Protected TFs deal an additional three damage to corvette and frigate targets, this damage cannot be increased in any way. Destroyer Group[Turbolasers] (Cruisers or a capital ship): Focus Fire Green: The TF can target an enemy ship and subject it to a withering hail of turbolaser fire. Ships can only survive so long under such a brutal attack (see damage tables below). Veteran: More potent turbolaser gases and higher quality crystals allow the ships to better chew through enemy shields. Focus fire damage against shield health is increased by two points(One point each for cruisers). Elite: The TF can put all power to weapons, doubling the damage it causes with focus fire, but also doubling the amount of damage it takes that turn from enemy removal attacks. Destroyer Group[Rail guns] (Cruisers or a capital ship): Focus Fire Green: The TF can target an enemy ship and subject it to a destructive barrage of rail gun fire. Ships can only survive so long under such a brutal attack (see damage tables below). Veteran: The TF has been allocated special armor piercing rounds for targeting heavily armored ships. Its focus fire damage against hull health increases by two points(One point each for cruisers). Elite: The TF can break formation to capitalize on more lethal attack vectors. Doing this allows it to do double damage, but it is also overextended for the next round so it loses any attached escorts and enemy task forces do not suffer penalties for stacking focus fire attacks on it. Destroyer Group[Missiles] (Cruisers or capital ship): Focus Fire Green: The TF can target an enemy ship within range and subject it to an explosive salvo of missiles. Ships can only survive so long under such a brutal attack (see damage tables below). Veteran: The TF has been allocated specialized HE cluster bombs for targeting corvettes. When the TF uses Focus Fire on corvettes only in a round, they do double damage. Spillover damage to other non corvette ships is reduced to zero. Elite: The TF may treat its focus fire damage like a bombers inbound action, allowing it to ignore cruiser and capital escorts but making it vulnerable to reduction by corvettes and interceptors. Covert Strike Force (One stealth cruiser): Silent Hunters Green: The TF uses stealth armor and sensor baffling countermeasures to prowl unnoticed along the edges of the battle. As long as the cruiser does not engage, each round they can bank three points of damage while stalking an enemy TF. On the TF commander’s order, the banked damage can be applied to a target ship’s hull integrity, ignoring support ships and shields. Banked points are not lost if the TF disengages to avoid scans, but are lost if the target is destroyed or the TF starts stalking another target. Veteran: The TF has a cloaking device, allowing it to hide even after its initial discovery. Elite: The TF can bank four points of damage instead of three. Asset Denial Force (Cruiser with frigate and/or corvette support): Surgical Strike Green: A heavy ion cannon barrage disables one unshielded ship for a turn. Disabled ships cannot use abilities, provide support or escort, or issue additional starfighter commands. Veteran: The task force declares its target for the ion cannon barrage after actions are announced but before they resolve. Elite: The TF has an experimental new type of hyperdrive that allows it to choose to ignore interdiction fields and make precise micro jumps, allowing for constant repositioning. The task force can ignore supporting and escort ships for its ion cannon attack, but only if the target is not the same one that was targeted last turn. Hellriders (Corvettes): Hit and run tactics Green: The corvettes can engage cruisers and capital ships to support either a focus fire or bombers inbound removal ability. The targeted task force can either choose to focus on the Hellriders, costing the Hellriders six corvettes but doubling the base value of focus fire and bombers inbound on the enemy task force, or they can ignore the corvettes and take three hull damage as the corvettes exploit vulnerabilities on the ship’s flanks and aft sections. Veteran: Hellrider formations tend to draw the most brash and aggressive captains, risk takers that owe success to high stakes gambles rather than experience and discipline. This task force has a reputation that makes recruiting these men and women easy, and does not suffer experience reductions from heavy losses. Elite: Gut churning space acrobatics allow the Hellriders to cap focus fire losses to four corvettes per enemy damage ability use. Med/Eng Support Cluster (Frigates): Guardian Angels Green: As long as the task force doesn’t engage the enemy, it is considered a war crime to target them. At the end of battle, the Task Force leader picks one allied Task Force that suffered Heavy Losses, the consequences are negated for it. Veteran: At the end of battle, the Task Force leader picks one allied Task Force that suffered Heavy Losses, the consequences are negated for it. He or she also picks one allied task force that was destroyed, that Task Force is instead treated as having suffered Heavy Losses. Elite: At the end of battle, the Task Force leader picks two allied Task Forces that suffered Heavy Losses, the consequences are negated for them. He or she also picks one allied task force that was destroyed, that Task Force is instead treated as having suffered Heavy Losses. Mobile Disruption Escort (Corvettes): Aggressive Defense Green: Coordinated and highly disciplined evasive maneuvers effectively translate to corvettes in this TF having a second point of hull damage. Veteran: Rather than attaching to an allied task force to cover it like normal for escorts, the MDE can attach to an enemy TF with removal abilities and force it to target them first. If the enemy TF is a carrier group, its bombers inbound action is treated as going through an additional corvette screen. Elite: Localized jamming causes the targeted TF to be unable to participate in coordinated attacks with its allies, and the MDE corvettes are now considered to have three points of hull damage for the purpose of removal abilities. Rapid Intervention Escort (Cruisers) Deadly Response Green: Halve removal damage if the TF is not attached to the same allied TF it was last round, or if it is currently not escorting any TF. Veteran: The TF focuses shields to front and intensifies forward firepower. When covering a new task force, it does removal damage to an enemy TF that is actively targeting or targeted the escorted TF in the last round. Elite: The TF decides which ally it will support after actions are declared but before they resolve. Heavy Brawler Escort (Capital ship): Hammer and Anvil Green: The TF has been heavily uparmored, and has an additional ten hull points. Veteran: The TF uses its heavier armor to close the distance with threats and engage them at close range with weapons designed for high damage at short range. Non artillery and detected task forces that attack ships being escorted by this TF or the TF itself take three removal damage in return. There is no limit to how many times this damage can be triggered per turn. Elite: The TF adds an additional damage to its counterattack for each non artillery and detected ship that attacked it or the TF it is escorting this turn. Fleet Command (Capital ship, one per fleet under the command of the grand admiral, the grand admiral does not need to use his or her flagship, but only they can command it if it is on the field): Flagship The grand admiral picks one upgrade to start, and selects a new upgrade at a rate of every two battles plus the number of current upgrades. Since the upgrades are specific to the ship, abilities that prevent veterancy loss cannot be used on the flagship. Axial Weapon: The ship may perform Focus Fire as if it was a Destroyer Group(Turbolasers). Target Saturation: The ship is flanked by a number of up armored and heavily shielded transports used to provide cover, halve focus fire damage to it. Precision Deployment: The ship house a small gravity well generator that can be used to precision deploy fleet assets, but this damages their hyperdrives, preventing them from being able to withdraw for the rest of the battle. Ultra-Heavy Flak Cannons: The ship carries a network of remorselessly deadly flak weapons. Treat the flagship as supported by corvettes. Meditation Chamber: Force Users can use these specially designed rooms to increase the efficiency of their forces, either gaining an additional Starfighter action or allowing two task forces to choose the same target for focus fire without penalty to damage. Citadel Overshield: Superior shield management prevents attacks that ignore shields from going straight to hull damage, instead being treated as regular attacks. Pocket Dreadnought: The flagship is far larger than a standard capital ship, allowing for heavier armor and more powerful shield generators. This translates to an additional ten shield and hull health.
  3. Fleet Rules Each player participating in a fleet battle commands their own Task Force(TF). If the numbers are uneven, then the admiral with fewer task forces can either choose to take a number of “Green” task forces to create an equal conflict, or request a secret win objective from the mods if it makes narrative sense to do so. No engagement is ever considered to include any faction’s entire fleet, and players can enter subsequent battles even if their last task force suffered total destruction. Player commanders are responsible for their task force’s ship composition, names, traditions, and portrayal in the RP, not to mention their actions on the field. All ships in a task force are considered to be overhauled to function at “modern” levels to perform their duties in a task force, so if players like the look of an older ship like a Venator, they can use it without having to worry about the shield generators being outdated. The scale of a battle is classified as one of three tiers, skirmish, sortie, and engagement. At skirmish level, each player controls a single task force, planning with others is vital for any sort of synergy within fleets, and it’s less likely for a task force to get vaporized out of left field. Sorties allow players more room to experiment with task force combinations and the use of defensive task forces with two task forces per player, but massed firepower becomes more readily available at this point and it’s easier for players to lose a task force when they aren’t expecting it. Engagements are meat grinder affairs of chaos and shattered plans with each player running three task forces, allowing for players to experiment with more exotic and situational task forces, but the firepower involved means that tactics are often upended in a massive turbolaser barrage. Players are encouraged to plan out task forces in advance, and new task forces that are posted before the start of their first battle with named ships and a backstory are treated as having already participated in a battle in terms of progression. Task forces gain levels from participating in fleet combat, Any PC led task force starts at Green, needs two battles for veteran, and three further battles for elite (As in, it takes five battles in total to gain elite status). A task force that loses over half of its ships (or suffers 50% hull damage in the case of capitals and specialist ships with support) is considered to have suffered heavy losses and must skip the next battle to undergo repairs and train replacement crew, and a task force that is wiped out loses a rank of veterancy unless it has a bonus to prevent that or is already at Green, in which case advancement to next rank is reset. Withdrawing is a full round action, but can prevent the loss of valuable experience and abilities. The fleet’s admiral can order “unowned” task forces to retreat. Only matched PVP battles give experience, practice battles, battles against NPCs, and narrative battles will not provide experience. Commanders are expected to maintain lines of communication and goodwill to the opposing players. All fleet abilities are announced at the beginning of the round (in secret) and resolved at the end of the round to represent simultaneous events rather than each post being slightly later in the timeline. Players that fail to meet the three day rule requirement are assumed to repeat their last action if possible. If it’s the first round, their commander is assumed to have failed to react promptly and/or the crew was caught unprepared and they make no action. Since all actions are determined at the beginning, and resolved at the end, post order of combatants is irrelevant as long as they post in the round, and the three day countdown goes into effect at the start of the round. Fleet commanders post actions once the round is up, with players optionally posting their more in depth narratives afterwards. Throughout the rules you will see references to removal, targeted removal, and damage abilities, these all refer to Task Force abilities and starfighter actions that allow ships to do measurable damage to each other. This is not to say that other ships aren’t actively firing their weapons or otherwise engaging the enemy, just that these task forces and bombers are specifically designed to overwhelm shields and compromise hulls. Rather than cluttering the process by trying to track every single ship’s attacks, we’re focusing on the heavy hitters whose role it is to destroy other ships, while letting other ships focus on different aspects of fleet combat. Up to three task forces can focus fire on the same enemy task force, but for each attacking task force after the first there’s a cumulative minus two penalty per task force to total damage inflicted, representing too many ships getting in the way of each other. Some task forces in this list mention that they are supported by smaller ships, such as the Interdiction Cadre. Leaders of these task forces can choose to reallocate removal abilities such as Focus Fire from their key ship to other ships in the task force to represent other ships tanking fire to keep their key piece on the field. As mentioned before, support ship losses do not count towards determining whether the task force has suffered heavy losses. Another form of defensive options are escorts, task forces that can attach themselves to other task forces to allow their ships to serve as support. Cruiser and capital escorts serving as support cannot intercept bomber attacks, but frigates can, and corvettes halve the damage of bomber attacks(and attacks described as being similar). Removal abilities that overkill a target with damage have the excess distributed to another target in the task force, and if necessary however many more targets are required to account for all of the damage. If the task force is destroyed entirely, the remaining damage is lost. In addition to any fleet assets they control, each fleet commander will also have a starfighter command to use each round(Some task forces allow for additional commands). This system does not track squadron numbers or ship carrier capacity, so there is no optimal meta ship pick that will maximize starfighter effectiveness. For more information see the list of commands below in the mechanics sections. A task force can arrive late to a battle. When a task force jumps in the enemy is made aware of ships exiting hyperspace at the beginning of the round (but not what those ships are) and have the opportunity to assign abilities to target them. If enemy sensors are jammed they lose the option to make an initial response. If comms for the side that is bringing in reserves are not jammed, the new arrival can perform an action as normal for the round. Some task forces (Interdiction cadre and Command Group at the time of writing this)can allow reserve forces to do precision jumps into the battle. Provided that comms are not jammed, the reserve task force can ignore support ships and escorts for the round that they jump in. If the task force is a carrier group and chooses Bombers Inbound, the starfighter action ignores support ships as well, representing the ships jumping in already in attack formation. Ships that use precision deployment have damaged their hyperdrives and cannot withdraw early (If both sides have ships stranded this way and no longer wish to fight they can agree to mutually disengage until repairs are completed). Some task forces are composed of ships with stealth armor or cloaking devices. For enemies to target them they must first find them through scanning. While every stealth system has a “tell” on certain frequencies, finding it takes time. At the beginning of each battle, the commander of the stealth task force picks a number between one and ten, this is their “tell” frequency. Task forces can scan their immediate surroundings and pick a number, if the number is the same as the stealth task force, and the stealth ship is stalking them, the stealth ship becomes targetable for the rest of the battle. Escorts share the same space as the task forces they are attached to, effectively giving a second guess for a high priority target each round. Additional scans are gained from using the combat air patrol starfighter action and if the concealed ship opens fire. If sensors are being jammed by an allied EW ship, the stealth ship has a second frequency tell that must be guessed before they are revealed. Ships with cloaking can change their tell frequency in the round as a full round action, meaning they can recloak, but they have to survive the round first. Cloaked ships cannot reuse an already discovered tell frequency, even if the discovered tell was for an allied ship. Hidden ships can go cold, not performing any actions for the round, to avoid scans for that round. Each side has one flagship that can be commanded by the grand admiral. The flagship can earn a variety of powerful upgrades, but if it is destroyed, all upgrades are lost. Furthermore, if the flagship is destroyed then the following round actions for that side are resolved after the opponent's, representing confusion and panic from the loss of such a powerful symbol. Mechanics Ship scaling A Task Force is 6 points worth of ships. One capital ship is 6 points, meaning that it comprises the entire task force. One cruiser is 3 points, meaning that a task force can either have two cruisers or one cruiser and smaller support ships. One frigate is 1 point. Six corvettes are 1 point. Removal effects and ship health Ship shields and hull by type Corvette: 1(This is not to imply that corvettes don’t have shields, just that the scale of firepower we’re measuring makes them irrelevant.) Frigate: 3/3 Cruiser: 9/9 Capital: 20/20 Damage per by ship type Bomber Wing: Varies by size of target, damage goes directly to hull unless abilities prevent it (Frigates: 1, Cruisers: 2, Capitals: 3) Cruiser: 4 Capital: 6 Starfighter Actions Each side gets one starfighter action per round, with some task forces providing additional ones. Bombers Inbound: The fleet’s bombers move to engage a frigate or larger ship, doing direct removal damage. When bombers target ships supported by corvettes their damage must go through shields before doing hull damage. Interception: The commander issuing the order picks two task forces, they cannot cannot be targeted by bombers for this round. Combat Air Patrol: The starfighters assist with locating potential hidden enemies, allowing for an additional scan of a task force’s area. Fighter Escort: Supplements bombers inbound, so only usable if the fleet can use more than one starfighter action a round. Snubfighters escort the bombers, making interception and other anti fighter abilities halve damage rounding down instead of stopping bombers completely.
  4. 7. Glossary of terms 2HK: 'two-hit kill'. A previously popular maneuver in which a player posts attacking, allows a return post, and then kills their opponent. Now illegal and will be nulled if used. Alias: any account past one's first used to create and RP with a new character. Alias-stacking: Posting with two or more accounts in the same thread consecutively, especially when acting in concert. Not permitted. Asset Points (AP): Currency used by factions to purchase assets such as fleets and planetary defenses. Duel: a series of three or more posts against another character or characters in which one attempts to best an opponent in combat (or conceivably some other way). Mod-approved and therefore legal. FU: 'Force-user'. A character who uses the Force. Godmoding: any use of unrealistic/overpowered measures, either in combat or without. In a duel/killshot situation, godmoding is very much frowned upon and will severely affect one's chances of winning the killshot/duel. IC: 'In character'. This refers to all actions taken within the universe of this role-playing game, by one's character rather than oneself. Killshot: an attempt to kill, capture or disable a fellow character without first engaging them in a duel. Mod-approved and therefore legal. NFU: 'Non-Force-user'. Any character who is not particularly sensitive to the Force. NPC: 'Non-player character'. This is any person which exists in the galaxy who is not a player character. This includes your average citizen or a nameless soldier, and together they make up the backdrop of the roleplay. Null: The act of a moderator reversing/canceling an illegal action taken within RP. OHK: 'One-hit kill'. An illegal maneuver in which one tries to kill/capture/disable an opponent in a single post. These are not permitted and will be made null. OOC: 'Out of character'. This refers to all interactions between players that is not explicitly narrative that characters could know about. PC: 'Player character'. Any character that exists in the RP that represents a player. PCs are the bread and butter of the Roleplay, its cast of heroes and villains. RP: 'Roleplay'. A blanket term for Jedi.net's roleplaying game. Also 'to roleplay'. RP'er/RPer: 'roleplayer'. Any person who participates in the JediRP role-playing game. Ruling: A Moderator's judgment on a killshot/duel or any other situation requiring a Moderator's attention. Rulings are final and will not be changed. Three-dayed: to kill somebody, or be killed by somebody, as a result of not responding to a duel post/killshot after three days. WBS: 'Welcome, Beginnings and Suggestions'. The previous name for the forum which roleplayers use to discuss gaming mechanics, ideas, comments, and concerns. Now titled the OOC Discussion forum, you may still see some old users refer to it by the old initialism. Back to the F.A.Q. Table of Contents
  5. 6. Miscellany (a) Ysalamiri -Only PCs OR one person of their accompanying retinue can carry ysalamir. -Anyone carrying a ysalamiri must account for the bulk and weight of an adult, full sized version of the creature, and it must be properly situated on a nutrient frame, no more lizard in a lunchbox antics. -Constructs and amulets can function internally at reduced capacity for one post in range, then go to barely functional. They lose any external functions immediately. Reanimants treat ysalamir like vampires treat crosses, they keep them at bay but do not destroy them. Factions have a yearly cap of ten ysalamir that they can harvest/maintain at one time. If those ten are lost in battle before the year’s end, the faction will have to cope without. Ysalamir cannot be stolen by another faction as a work around, and new factions will start with their full allotment at faction creation (Creating new factions as a workaround to running out of ysalamir will not be tolerated). Faction leaders have final say on ysalamir use. Factions can lend out ysalamir to freelancers, but not other factions. Design notes: This iteration of the ysalamir rules is designed to set up a risk/reward situation for ysalamir. You can go all in and give everyone ysalamir, but doing so risks burning through your allotment if there is a shutout. The current number allows for a full faction to wipe twice before running out, which we felt was a fair starting point for the rule, but we can adjust that number as needed. We also addressed some situations that would otherwise make ysalamir OHK vehicles for certain NPC types and PCs, closed some exploits regarding fortified and teacup ysalamir, and addressed ysalamir spam. Ysalamir are still a powerful means to counter Force users, but this prevents them from being omnipresent to the point of stifling fun for other players. (b) Neutral locations - Currently, the only completely neutral location in RP is the 'Last Call' cantina. No violence or Force use of any kind is permitted in this location, and such actions will be nulled. The advantage is that you can treat this location as a safe zone. - Although other locations may be considered 'IC'-neutral, mods do not enforce this 'OOC'. This functionally means that although characters consider violence there a no-no, it may be (and, on occasion, is) attempted. (c) Use of NPCs The use of NPCs is allowed in this game, but with certain restrictions. (1) Flavorful use of NPCs is allowed, without restriction. For example, if a PC enters a cantina, there is nothing wrong with using NPC characters that one would normally encounter for basic interactions. A PC is allowed to describe the atmosphere of the cantina, with the server droids and dancers and whatever other patrons are present. A PC exploring the Under Levels of Coruscant would be allowed to interact with beggars. Sith PCs in the Sith Temple can torture NPC acolytes. There is no tactical gain from such interaction. (2) Tactical use of NPCs is allowed, but restricted. For instance, having a body guard, or banker that garners resources, or soldiers on patrol constitutes tactical usage of NPCs. PCs that are members of specific factions are allowed to use their faction's NPCs tactically within reason. Within a faction's own territory, members of that faction may tactically use NPCs even without a PC present. However, when traveling outside of faction territory, a PC must accompany the NPCs. That said, PCs that are not members of factions, cannot use NPCs for tactical gain. Unless: (3) PCs that are not members of factions may employ NPCs from factions, for tactical use, if permission is obtained from those factions. For example, a PC that owns a cantina in Mos Eisley may hire NPCs as guards or bouncers. However, the factions will control their loaned out NPCs. For example, if the Mos Eisley cantina gets attacked by Jedi, a member of the faction will control the NPC guards. Or, if the owner of the cantina is already a member, he or she may control the NPCs. (4) The faction's leadership has the final say on how the faction's NPCs would be employed for tactical use. For example, it might be in the faction's best interest to limit NPC use to only certain PCs. Perhaps the newest Jedi could control a handful of apprentices, but not the temple guards. (5) Ultimately, allowing factions to control their own NPCs ensures a realistic portrayal of massive interstellar organizations, which would understandably sustain numerous members and workers. For instance, temples have guards. Organized crime has assassins. Law enforcement has agents. A faction's headquarters has more security than a cramped hideout. Such examples are realistic and appropriate. However, the ability to lead and control NPCs does not permit personal armies or individuals entering duels with squads of droids and soldiers. The mods retain discretion in determining what is appropriate and what is disproportionate or unfair regarding the use or acquisition of NPCs. The essential element of this game is the unique characters interacting with one another, not controlling and owning garrisons of droids or clone militaries. (6) Utility NPCs are NPCs with character sheets that serve supporting and world building roles like trainers and government officials. These NPCs are not meant to be used in combat or in personal storylines, and will avoid conflict with PCs when possible (Other than Sith trainers potentially beating down overconfident apprentices). Faction leaders have final say over the portrayal of utility NPCs. Bodyguard NPCs for Support characters: Characters that specialize in abilities such as healing and buffing to the point where achieving victory in a duel is practically dependent on allies to use their powers on will be allowed to have a bodyguard NPC that functions like a tactical NPC with extra layers of plot armor. As long as the PC is in a combat able state, the companion is able to persist provided its owner did not make it perform a suicidal or otherwise incapacitating action. Bodyguards are not secondary PCs, instead think of them as tools to showcase a support character’s abilities. Bodyguard NPCs require mod approval. Companions/Champions: Essentially backup combat characters that can be sent to fight in battles on behalf of your main PC if they are mid story or otherwise indisposed (not including death or capture). A player can never have more than one of these alternates at a time, but they can replace him,her, or it upon death or retirement. Replacement has a six month cooldown after creation to prevent new character spam. Alternates are treated as PCs of equal level to the main PC, except for faction leaders, their alternates are treated as master equivalents to preserve the impact of their arrival on the field. Use of a champion requires active and loyal membership in a faction. Supporting Cast(Rework of claimed non tactical NPCs): Non combat NPCs tied to a PC’s storyline. Supporting cast can be of rank in the character’s aligned Force user faction, but no higher than a step below the PC’s current rank(Note the distinction that they don’t have to be the same faction, just the same side, so for instance a rebel can be on friendly terms with a Jedi healer). These NPCs have the combat capabilities of a heavily sedated porg regardless of rank, and will flee if combat comes to them. If using Force powers will help an FU supporting cast NPC escape they can use as their rank dictates, but any attempt at combat or otherwise interfering with combat immediately reverts them to hopeful rank and causes them to fail. In any other state than actively participating in combat, supporting cast NPCs have plot armor. Supporting cast cannot be used to access secure areas of factions that the PC does not belong to. Golden Rule of NPCs: No amount of plot or rules armor will protect any character from a suicidal action. Misuse of NPCs can result in their status being changed or disciplinary action. (d) Cortosis Due to varying examples in canon, we have decided that Cortosis will work the following way on our board: - Cortosis Alloy(s), as seen in KoToR, functions as expected, it is lightsaber resistant and suitable for making vibroblades and similar weapons from to properly defend against lightsabers. -Raw/Pure/Refined Cortosis, or basically any iteration of the material not mixed in an alloy, significantly drains the power from a lightsaber with each hit. Lightsabers retain the ability to block, almost like in a training setting, but immediately lose the energy necessary to cut through materials. This can be fixed by simply power cycling the lightsaber (turning it off and on). Several hits and the RPer should consider having to swap out the lightsaber's power cell for realism's sake. This kind of cortosis is prohibited from being used in weapons/bullets/any offensive capacity designed to automatically imply deactivation/power reduction of a lightsaber in a chain effect to subvert another RPer's agency to react. Basically, don't use it in weapons.
  6. 5. Factions The Empire and the Alliance The various factions and organizations of the RP can largely be sorted into two megafactions, the Empire and the Alliance. These two sides serve as anchors for the other factions and groupings for fleet assets, while also defining inter-faction interactions. While what if scenarios are a fun thing to theorize about, the staff would prefer to keep to the traditional political breakdown, both for accessibility to new players and to maintain balance in the RP. The Core Factions and Faction Management There are five core factions in the RP that help maintain forward momentum for the plot; the Jedi, the Rebels, the Empire, the Sith, and Black Sun. During times of low player population, recruiting for these factions will take priority, and the creation of spin off factions will be limited or possibly even restricted. Black Sun is considered a neutral faction, serving as a starting point for effectively unaligned bounty hunters and other mercs. Faction leaders have the greatest authority over the narrative of their factions, and can automatically veto attempts to compromise or usurp assets through unauthorized use of NPCs or other faction resources. Factions are distanced from the actions of PCs depending on the faction rank of the PC. Apprentices YOLOing enemy bases can largely be handwaved away, while knights and lords share more accountability with their faction. Master rank characters are considered to be faces of the faction and as such their actions carry the most weight for good or for ill regarding public opinion. Faction leaders have the power to demote faction members, usually on account of extended absence, a character or player demonstrating the need for additional training before they are ready for the rank, or the character is continually acting in a way that is harmful to the goals and/or ideals of the faction. Faction leaders themselves can lose their position through inactivity, with the seat being considered open after a month of inactivity. Otherwise, each faction has its own methods for resolving the transfer of power, and players are encouraged to keep to tradition. In severe cases of misconduct, the mods may remove a player from a leadership position to protect the community. Players can only hold one leadership position at any given time in the factions, regardless of the number of aliases they possess or the standing of those aliases within the factions. We want to make sure that older players, who tend to have both the connections and aliases to secure multiple positions don’t unintentionally gate off political advancement for other players in a faction, or have to compartmentalize their player knowledge due to holding commands in opposing factions. If a character decides to switch sides, the betrayal should focus on personal consequences and not be used to steal assets or compromise secrets or security for the faction being betrayed. While this is fairly unrealistic, it prevents the weaponization of traitor characters and also prevents the act of betrayal from having too much mechanical weight. Players can create subfactions within the factions freely, as long as the subfactions are identifiably of the parent faction, and maintain loyalty to the faction leader. In mechanical terms, subfactions should be cosmetically different but not mechanically different. In other words, they should not be treated as a prestige or superior form of the faction, or possess abilities available only to them regardless of an outsider’s skill or training in an attempt to replicate the power or skill. Organizations Players with characters that have achieved master rank or equivalent in a major faction can create organizations. Organizations are groups of individuals that are valuable to worldbuilding, but don’t function well as full fledged factions. The creator of an organization has authority over its narrative, just like how faction leaders have authority over the narratives of their faction and NPCs. Organizations that predate this rules system can only be claimed by their creator. Organizations can have locations associated with them, protected by sufficient security to protect them from basic intrusion both physically and technologically, however players shouldn’t expect these places to function as strongholds. On the flip side, organizations are low profile enough in game that attempts by factions or players to target them without just cause will be reviewed by staff and may be reprimanded as trolling or griefing. (c) NFU Progression and Ranks NFU Ranks (Names are generic and can be changed according to faction preferences) Grunt career path Recruit (Starting Rank) Access to blasters, thrown grenades, vibro weapons, and basic armor. Veteran (3 months active roleplaying plus a defining moment such as a well written duel or competent world building coming to fruition that is acknowledged by a veteran/line officer or higher rank peer) Access to heavy weapons, launchable grenades, jet/rocket/repulsor packs, lightsaber resistant melee weapons, and powered armor of standard materials. Legend (Six additional months of active roleplaying plus a defining moment acknowledged by an NFU faction leader) Access to exotic weapons, powered armor made of rare materials like phrik, and personal shields. Command Style (Officer) Character variant rules Junior Officer (Starting Rank) Access to pistols and light armor. Can lead squads of their faction’s basic troops. Line Officer (3 months active roleplaying plus a defining moment such as a well written duel or competent world building coming to fruition that is acknowledged by a veteran/line officer or higher rank peer) Access to personal energy shields. Access to rifles and medium armor if the character already went through the Grunt career path. Can lead squads of their faction’s advanced troops. Career Officer (Six additional months of active roleplaying plus a defining moment acknowledged by an NFU faction leader) Access to high quality light power armor. Can lead squads of their faction’s elite special forces. Limited to pistols and light armor at the beginning, officers can branch out to rifles and medium armor at Career Officer rank, unless they went through the “grunt” character path first, in which case they can make the transition at veteran. Some officers carry melee weapons as symbols of office and to assist with signalling commands, but two semesters of vibrofoil fencing at the officer training academy doesn’t always translate fantastically to the no holds barred close quarters fighting found on the battlefield.
  7. 4. Force Users and the Force (a) Getting started - New users may indicate that their character is 'Force sensitive' in the appropriate section of their character sheet. However, they cannot be trained in any way, and may not make use of the Force except in a very vague sense ('bad feelings', intuition etc.) - New users are not permitted to begin with a functional lightsaber. A character can have a lightsaber as a family heirloom, but it must be in a state of disrepair requiring training to fix. A new user who attempts, untrained, to use such a lightsaber does so at their own risk, as covered below. - NFU's and lighsabres: NFUs are allowed to wield lightsabers in combat if desire and necessity allow it, though the inherent dangers of using a weightless weapon that gains mass and momentum when striking a solid object or energy barrier must be considered, so use at your own risk to life and limb. Microfusing the circuits and aligning the crystals requires the Force, so NFUs may not create their own lightsabers. (b) Progression - Once you have been chosen to be trained by a Lord/Master (see 'Force-user ranks' below), you have to train actively for at least three months to be able to take the trials to become a Knight/Lord (It often takes longer - this depends on your master's deeming your readiness to take the next step and the rate that both of you post) - Once you have become a Knight/Lord, you will need to actively roleplay and "train" your character for an additional six months (nine months cumulatively since starting, assuming three months to reach Knight/Lord level) to become eligible to be a Master, and you must train at least one apprentice to Knight/Lord-level. Furthermore, you must be assigned and complete a trial set by a current Master-level character of your chosen faction. © Force-user ranks JEDI: Padawan Knight (three months active roleplaying plus trials) Master (six additional months active roleplaying plus recognition and trials) Council Member: must be chosen by current Council Members or named by the Grand Master Jedi Grand Master: the head of the Jedi Order. Often chosen by his or her predecessor or by the Jedi Council. SITH: Apprentice Lord (three month' active roleplaying plus trials) Master (six additional months' active roleplaying plus recognition and trials) Unholy Trinity/Inner Circle: Chosen by the Dark Lord Dark Lord: must defeat the current Dark Lord in mortal combat. If there is no current Dark Lord, then the Sith Order will decide in-character how to proceed.
  8. 3. Ship Rules - Ship stats should be posted in one's 'character sheet' thread. Personal ships 1. Size must be smaller than a corvette; a light freighter (such as the Millenium Falcon) is appropriate 2. No cloaking devices. 3. No quantum armor, ablative armor/shields or other forms of invincibility. No turbolasers regardless of the canon listing, use heavy laser canons. 4. All major upgrades must be run past a mod, so that we can verify the whether it is feasible and fair for the RP environment.
  9. 2. COMBAT RULES (a) Combat Arrival and Interference In order to approach another character for combat or for any other adversarial reason, you must consider the realism of the time necessary to arrive, especially when factoring in the time of space travel. Obviously you can't fly across the galaxy to interrupt shots fired or interfere in a duel that is only taking seconds or minutes. For clarification, there are two speeds of potential arrival: - Quick Arrival indicates that you can arrive reasonably fast. For instance, if a group of Black Sun gunners attack a city, it's reasonable that someone close by might be able to get there within an hour or so, or fast enough to join a scenario already in progress. In order to determine whether you can arrive quickly, look at the Official Galactic Map. If your current location is within 2 grid squares of the destination, you may arrive quickly there. Diagonals count the same as directly adjacent squares. For example, if you are on Dantooine, you may quickly travel to Dubrillion, Artus Prime, Thalassia, Yaga Minor, Altyr V, Dathomir, Serenno, and Yeveshi Minor. However, if you do not qualify for a quick arrival: - Standard Arrival indicates that you could arrive, but are delayed by the standard hassles of having to fly through space. Most conflicts are resolved in only a few hours, and you can't realistically arrive in time to interfere with such situations. However, after a prolonged situation, anyone could typically arrive after realistic time has passed. For example, if a group initiates and maintains a siege on a specific location, a character could arrive sometime later, since the immediacy of their attack was not an issue. Common sense takes over. If someone attacks a location and posts that they are merely then going to sit and wait, then they are fair game. Essentially, anyone can arrive in any conflict situation, as long as it's realistically delayed. If you have any question about whether or not you should wait, ask a Mod. Lastly, and perhaps most importantly, these rules on timing are only for adversarial situations. If two people agree mutually to fight, and also invite someone to join in, that is perfectly acceptable. If characters are working together, then this isn't an issue either. These rules exist to prevent someone from unrealistically spoiling another's timeline, not to restrain characters that are RPing together. (b) Duels - Duels are a combative, multiple-user confrontation in which each party has a pre-determined number of posts (three or more) to try to best their opponent. - The protocol for a duel is to propose one to one's opponent using parentheses, followed by posts numbered according to sequence within the duel. The rough sequence for this is as follows: A: ((duel?)) B: ((Accepted)) ((1)) A: ((1)) B: ((2)) A: ((2)) B: ((3)) A: ((3)) - Following the conclusion of the participants' duel posts, they may then make a ruling request in the 'ruling request' thread. A mod will then rule upon the duel in a manner similar to a killshot, noting techniques, successes and failures. The winner may then post a final post- in this post they may to anything to their fallen opponent with impunity, including capturing or killing them. - You should not post your opponent's actions in a duel AT ALL. This includes posting damage caused, movements and speech. The correct protocol is to post initiating an attack or attempting a maneuver, but refraining from posting how it affects one's opponent. - You may not kill or completely disable your opponent until the duel is over and you have been declared the winner. - If you lose the duel, you may not post again until your opponent has posted. The usual rules for death apply. - If the winner does not post within three days, he or she forfeits his or her right to kill/disable the opponent. The loser is free to act again, but may not kill their opponent. They may initiate a second duel/killshot, however. © Killshots You can request a killshot at any time, typically after at least one set-up post. Your set-up post(s) can be as simple as popping the strap on your blaster holster, or as complicated as defeating security measures, climbing a tower, setting up your sniper rifle, and aiming at the target. - The killshot should be requested in the following manner, at the end of your set-up post (or at the end of the last set-up post): <>, followed by a post in the 'ruling request' thread in the "Welcome, Beginnings and Suggestions" forum. - The attacked RP'er has one post to react in whichever way they see fit: if it's a subtle set-up post, FU's may detect the intent. If you're an NFU, I'll get to that later. Killshot defense posts should be suffixed with <>. - The mod will review the attempt and make a ruling based on the characters' experience, post quality, and number of set-up posts. - Your attempt may go one of three different ways: Killshot successful (Click spoiler for expanded explanation) - Following a 'killshot successful' post by a mod, the attacker may post a killing blow or otherwise injure or incapacitate the defender. The defender may post nothing. Killshot countered (Click spoiler for expanded explanation) - Following a 'killshot countered' post by a mod, the defender may post killing the attacker immediately, or they may choose not to. If the defender chooses to spare the attacker, they must post this so the attacker is not left hanging for a response for days on end. Killshot failed (Click spoiler for expanded explanation) - Following a 'killshot failed' post by a mod, the mod may choose to impose a situational disadvantage on the attacker, e.g. they may choose to allow the defender to disable/destroy the attacker's ship or equipment in one post, or capture the attacker in one post. The disadvantage to be imposed is at the mod's discretion. - IMPORTANT NOTE: THIS ABILITY CAN BACKFIRE ON YOU EASILY AS IT CAN GAIN YOU A QUICK KILL. BEFORE YOU INITIATE IT, THINK CAREFULLY ABOUT WHO YOU ARE ATTACKING, HOW WELL-DEFENDED YOU AND YOUR POSITION ARE, AND HOW FAR AWAY YOU ARE FROM YOUR ATTACKER. YOU SHOULD ONLY BE USING KILLSHOTS WITH A LITTLE PREPARATION IF YOU ARE VERY CONFIDENT OF YOUR ABILITY TO KILL THE TARGET; IN MOST INSTANCES YOU SHOULD BE USING AT LEAST TWO SET-UP POSTS. Supplemental notes on killshots (click spoiler):
  10. 1. GENERAL 1. No posting after yourself until whoever you are interacting with has posted, or three days have passed. If you are not interacting with anyone and need to post again, edit your own post (only to add what would have been the new post) and clearly mark the edit. If three days have elapsed since your last post, you may post after yourself regardless. 2. You may not kill or capture another PC without a mod ruling. This is done via a duel or a killshot (see below in combat rules). 3. Characters cannot physically be in multiple threads at the same time. This includes Force ghosts, etc. Comm messages and similar are fine. BETA FORUM: Because the timeline in this forum is not occurring concurrently with the main forum, your character may be physically here and in the main forum. For now, you may only have one ‘copy’ of yourself in the Beta forum, however this is subject to change. The Beta forum is still highly experimental and is a work in progress. 4. No alias-stacking for fleet battles under the false pretense that the aliases are controlled by different players. 5. If your character dies in combat by mod ruling, then he/she/it is dead for three days. There is to be no posting in RP proper for any reason. This includes spiritual visits, holo-recordings, NPC actions, or any other method of communication. You may post with aliases. If you choose to kill your character as part of a storyline, either for Force ghost interactions or otherwise, this rule does not apply. 6. You may not post another character's actions unless it is agreed upon by the other user and the mods have been notified. Please record the agreement and PM it to the mods, and any affected parties for ease of reference. 7. If you are engaged in a duel or combat action you have three days to make a response. If you fail to do so, your opponent is allowed to kill or incapacitate you to keep the RP moving. 8. Where there are three or more interacting combatants, take turns equally. This does not apply to PCs that are at the same conflict, but are not interacting. (Separate duels, etc.) 9. No editing a post if someone has posted after you in the topic, interacting or not. Not even for grammar/spelling. 10. Sharing accounts: All players with access must be listed on the character sheet, violations (other people than the ones on the list accessing the account or posting) are subject to bans. 11. Character creation rules, and a template for your character sheet, can be found here. The short list of rules can be found below, but be sure to read that whole thread before making your first character. Due to the move to IPB, the Moderators no longer have direct control over whether an alias can post in the RP because linked accounts allow bypassing of permissions masking for the newer account. This means players will largely be on the honor system, and because of this, should anyone be found guilty of intentionally trying to sneak items or powers past the mods that break rules, the consequences will be far more severe. You are still required to obtain approval from a Mod for any newly created character prior to posting. If you have a question about something, ask a Mod.
  11. TABLE OF CONTENTS 1. General rules 2. Combat rules (a) Combat Arrival and Interference (b) Duels (c) Killshots 3. Ship rules Personal ships 4. Force-users (a) Getting started (b) Progression (c) Force-user ranks 5. Factions, Faction Warfare, and Non Force User Progression (a) General (b) Faction Warfare (c) NFU Progression 6. Miscellany (a) Ysalamiri (b) Neutral Locations (c) Use of NPCs 7. Glossary
×
×
  • Create New...