Email the Thrawn's Revenge team Find us on Facebook Subscribe to us on YouTube Follow us on Twitter See us on ModDB
Those working on this mod do so in their own free time and for no pay.
Show your support for them by enabling ads on this site!


Endcar's Appendicitis Emergency Fund

Wednesday June 21, 2017

We typically don't post personal stuff of our team not related to the mod, however one of our 3D Artists had some serious medical issues recently. If you could take a moment to read, share, or if possible, support the gofundme, we would all appreciate it. ...

Read more »

ASC: We thought it was a ghost ship, until it opened fire...

Sunday June 18, 2017


Read more »

ICW/FotR: Microjump Preview

Thursday June 15, 2017

A quick look at another ability coming in Thrawn's Revenge: Imperial Civil War and Fall of the Republic, Microjumps. ...

Read more »

ICW: Empire of the Hand Preview Playthrough

Thursday June 08, 2017

I've begun my full Empire of the Hand playthrough on my channel, covering several of the new units, graphics and functions in 2.2. Episodes will be posted every Wednesday, Friday and Sunday. ...

Read more »

ASC: Imperial Remnant 1.1 Overview Video

Wednesday June 07, 2017

Continuing our faction video preview series for 1.1, Corey has just posted the Imperial Remnant's, covering their new tech and ship abilities. Next up will be the Hand, and finally, heroes. ...

Read more »

11th Anniversary Team Livestream

Friday June 02, 2017

Tomorrow (Saturday, June 3rd) at 3pm EST, Corey Loses will be hosting a stream to celebrate 11 years of Thrawn's Revenge with several members of the dev team (so far, Corey, Slevered, Dr Nick, and Pox, with potentially Robin, Endcar and Slornie). We'll be revisiting Imperial Civil War 1.0 while talking about future plans for Imperial Civil War, Ascendancy, and Fall of the Republic, mod history, and answering questions from the chat.If you wanna watch and join in on the chat or have some questions, click the link below: ...

Read more »

Single-Unit Retreat

Wednesday May 31, 2017

Did a quick video on the sing;e-unit retreat function coming up in ICW 2.2 and FotR 0.5 while prepping for my EotH preview campaign to kick off. ...

Read more »

Ascendancy 1.1 Overview & Testing Plans

Tuesday May 30, 2017

As I was compiling all the updates for this release cycle of our projects for the helpful new News Post Compendium thread on the forums, I noticed that while Ascendancy has had some very specific updates, we haven't done an overview of some of the more general changes yet. Because of the proximity of the 0.95 and 1.0 releases, which were primarily about setting up basic content, 1.1 is the first release where we really have had an opportunity to address some of the bigger points of community feedback, instead of just working on the basic content of the mod. hopefully this update will give a better idea of some of those features, as well as an overview of how testing and future releases will go....User Interface...First, one of the more common complaints against 1.0 relate to some of the icons- planetary icons aren't particularly clear, and unit icons tend to take up too much screenspace. We were attempting to simplify the information as much as we could, and also trying to address the icon situation in a way to get around the fact that Star Wars ships in the same faction tend to have a similar profile, making the Sins style less feasible. This was not always successful. The changes to presentation of the unit stacks/force indicators beside planets were also harder for some players to find. So, since the last release OzWolf has redone all of these aspects entirely; unit pips should take up less screenspace, hopefully still being clear enough about what they are, while maintaining the larger more prominent style for planet infrastructure, highlighting its importance and helping it stand out. We still feel that having just renders of the planets, while technically being the most "accurate" isn't always the most clear (especially when so many are primarily green), so we've tried to use some simple, clean symbols to represent them, as you can see below. We've already posted some screenshots in the past of the updated menus and such, so here are some more screenshots of some of the ingame HUD-related changes, including planets, unit icons, and all of that. Crucially, we've also played around with team colours. Hopefully these changes help more easily provide information to players than previous versions....Balance, Economy, Research & Factions Fleshed Out...For the fleshing out of the factions in terms of additional tech and abilities, I have been doing full faction profiles on Corey Loses (Hand and Remnant still forthcoming, so I won't say too much about that here, save that I have been bringing each faction up to at least 100 research options for 1.1, with plans to expand that as we figure out which gaps each faction needs to fill, and Bane & I have been filling all the empty ability slots from 1.0, which should help give some added flair and flavour to the different units and factions.Primarily, though, almost every single stat has been changed in a significant way. The cost and times associated with research have all been adjusted, which should help with the early game slog, while unit upkeep costs help to keep the late-game credit and resource overflow in check. While the stats are not yet final, and will be regularly tweaked up until release, we have a full spreadsheet with all damage, health, and other helpful values which should both help players understand how the units work, and help bring inconsistencies or outliers to the attention of the team more easily. Keep in mind, though, that while stats like this are helpful they don't always tell the full story (especially with abilities coming into play more). This spreadsheet can be found here, and will be updated as we approach release and beyond as we make further changes:Unit Stat SpreadsheetIt's not reflected in this spreadsheet just yet, but we've rescaled shield regeneration, significantly increasing the speed at which ships will recharge, which was far too low before. We also plan to do some alterations to ship ranges in the future, both to add some variation between units, and also to help combat be a bit more visible (right now ships are probably a bit more spread out than we'd like).Alongside this, of course, we've worked over the last year to resolve bugs with unit behaviour as they've been reported, including the VSD firing issues, along with trying to address some of the more abusive strategies. The function of starbases has been greatly expanded as well, and the Esseles-class Civilian Station has been removed. Stations, now being the Cardan (Remnant), Empress (New Republic), Validusia (Alignment, pictured below) and Oto (Hand), should now each be a lot more capable than the Command Station/Empress of 1.0, while still reflecting the unique flavour of the factions.When it comes to number changes like these, it's hard to really get across what we're doing without being able to play with them for yourself, bringing us to......Release Structure & Testing...A lot of the biggest issue with where the mod currently stands in our mind come as a result of how long it has been between releases, with 1.0 having been released essentially over a year ago in its beta form. In our experience with Imperial Civil War, while balance was still certainly a concern, it was not a primarily multiplayer or "competitive" game, which meant we could take longer to address some edge strategies that would be overpowered- having 6 months to a year between releases doesn't impact enjoyment as much. It also had a much more stable foundaction, being several releases in. In Ascendancy, with more moving parts and as a primarily-multiplayer experience and without such a long history of iterating on feedback, we need to be able to react more readily to balance or design issues as they arise, rather than waiting for the larger content release goals to be met. This is something we will be changing going forward. We will still be structuring the release of new content versions similarly (ie, not releasing the upcoming factions piecemeal), however within those cycles we plan to have a new release or patch to address any issues in game mechanics or balancing every 2-4 months, as necessary (on top of any hotfixes necessary at release). This has been especially obvious in 1.0 since, as I say, it was the first release, and therefore does not benefit from the ability to have been made and iterated on with larger amounts of player feedback.To that end, we will be starting a semi-open beta process on our forums at around the end of June. This will be done in two progressively more open stages. First, once we're satisfied we've caught the major bugs with our internal development and testing teams, we will be opening up the beta to members of the Admiral's Lounge on the forums. After a week or two weeks there, we will open it up to all forum members until we're satisfied that it's ready for release. To be clear, the entire point of doing a beta like this is to provide feedback before a full release to ensure a stable, fun release, not to simply play an early version. As such, we are setting it up in the way that is most conducive to managing that process, especially since we're likely gonna have to do a lot of explaining how to use GitHub. We will be setting up boards for reports, updates, changelogs and multiplayer matches during the process.We hope you're looking forward to giving these changes a try, and as ever, we're looking forward to hearing everyone's feedback.- The Thrawn's Revenge TeamFollow AscendancyForums - Facebook - Steam Group -  Mod DB - Twitter ...

Read more »

Release Cycle News Post Compendium (ICW 2.2, Ascendancy 1.1, FotR 0.5)

Saturday May 27, 2017

It can sometimes be hard to locate all of the news related to a current development cycle, so this thread compiles all of the relevant news posts in chronological order, for all of our projects.Imperial Civil War 2.2:February 7th, 2016: Faction Profile: Warlord ZsinjJuly 18th, 2016: Regime ChangeAugust 2nd, 2016: The 2.2 ManifestoSeptember 3rd, 2016: We Could Be Heroes- The Pentastar Alignment September 15th, 2016: We Could Be Heroes - Warlord ZsinjSeptember 24th, 2016: Era One - Galactic Conquest BreakdownOctober 13th, 2016: Era Two - Galactic Conquest BreakdownOctober 21st: Faction Profile: Greater MaldroodNovember 7th, 2016: Schism Events, Research, and Galactic Conquest Breakdown - Era 3December 7th, 2016: We Could Be Heroes - Greater MaldroodDecember 2nd, 2016: 2.2 Demo AnnouncementDecember 13th, 2016: Faction Profile: Eriadu Authority March 3rd, 2017: 2.2 Demo ReleasedMarch 6th, 2017: Beta Testing and We Could Be Heroes - Eriadu AuthorityApril 13th, 2017: EotH: Past, Present and FutureMay 26, 2017: GC Selection Layout UpdateAscendancy 1.1:May 31st, 2016: 1.0 Post-Release RoundupAugust 2nd, 2016: Ssi-Ruuvi Redux & Development ProgressOctober 15th, 2016: Fractured EmpireDecember 6th, 2016: Updated Faction Select ScreenDecember 10th, 2016: 1.2 Faction Profile: The Hapes Consortium (1.2 Early Look)April 13th, 2017: EotH: Past, Present and FutureApril 28th, 2017: Pentastar Capital Ship Ability and Tech OverviewMay 11th, 2017: New Republic Capital Ship Ability and Tech Overview]May 30th, 2017: Ascendancy 1.1 Overview & Testing PlansFall of the Republic 0.5:April 1st, 2017: FotR Teaser TrailerMay 9th, 2017: Fall of the Republic Announcement and FAQ ...

Read more »

Weapon System


Thrawn’s Revenge uses a representative system to assign appropriate weapons to different units and balance them according to, where possible, their canonical armament. The basis of this system is that, for any given ship or weapon-type, a single instance of that weapon counts as one pulse from a hardpoint. So, for example, if a ship canonically has sixty turbolasers, we could give it six hardpoints each firing ten pulses, or twelve hardpoints each firing five pulses, etc.

The armament of a ship is displayed in the form of Total Pulses/No of Hardpoints for each type of weapon it possesses. So, for example, the Imperial Star Destroyer’s 60/6 Turbolaser hardpoints translates into six hardpoints firing ten pulses in each round, whereas its 6/2 Dual Heavy Turbolaser becomes two hardpoints firing three pulses in each round. To compare this to another example, take the Venator-class Star Destroyer, with its canonical armament of eight Dual Turbolasers. Since we aren’t representing all sixty individual Turbolasers on the Imperial Star Destroyer, it would be unbalanced to set the Venator up with eight fully charged (10 pulse) hardpoints. Instead, we have given it four hardpoints firing two pulses each round. This system has been used for all space units, although starfighters and some anti-starfighter ships (such as the CR90 Corellian Corvette) are handled slightly differently.

Laser Cannons/Maser Cannons

Laser and Maser Cannons are weapons that fire bursts of particle beam energy. These weapons are of a small enough calibre to be quickly and accurately aimed at fast-moving targets such as starfighters. Laser and Maser Cannons are capable of damaging both hull and shields.

Weapon Type Damage (Normal) Damage (Heavy) Rate of Fire* Recharge Time*
Laser Cannon 2.5 3.5 0.2s 4s
Laser Cannon: Dual 5   0.2s 4s
Laser Cannon: Quad 10   0.2s 4s
Maser Cannon 3 4 0.2s 4s
Maser Cannon: Dual 6   0.2s 4s
Maser Cannon: Quad 12   0.2s 4s


Turbolasers and Megamasers are immensely scaled-up versions of Laser and Maser Cannons. Generally turret-mounted, they are commonly found on capital ships and space stations. Equipped with significantly larger capacitors, they can store and discharge far more powerful bursts of beam energy. They are primarily used for ship-to-ship combat because their size and slow target-tracking is ineffective against the small and fast targets presented by starfighters. Turbolasers and Megamasers are capable of damaging both hull and shields.

Weapon Type Damage (Normal) Damage (Heavy) Rate of Fire* Recharge Time*
Turbolaser 5 6.5 0.2s 4s
Turbolaser: Dual 10 13 0.2s 4s
Turbolaser: Quad 20 26 0.2s 4s
Turbolaser: Octuple 40   0.2s 4s
Megamaser 5 6.5 0.2s 4s
Megamaser: Dual 10 13 0.2s 4s
Megamaser: Quad 20 26 0.2s 4s

Ion Cannons

Ion Cannons are ranged weapons which fire ionised particles or plasma that can cause serious interference with the operation of electronics and computer systems. Ion Cannons are only capable of draining energy from shields and systems, they do not do hull damage.

Weapon Type Damage (Normal) Damage (Heavy) Rate of Fire* Recharge Time*
Ion Cannon 10 13 0.2s 4s
Ion Cannon: Dual 20 25 0.2s 4s
Ion Cannon: Triple (Trion) 25   0.2s 4s

Warhead Launchers

Warhead launchers are used to fire a range of self-propelled projectiles that can deliver considerable explosive power to their target. Concussion and Rhazor Missiles are able to target practically any unit, while Proton Torpedoes are restricted to Corvettes and above. All warheads cause damage to both shields and hull.

Weapon Type Flight Range Damage Rate of Fire* Recharge Time*
Concussion Missile 2200 18 0.4s 15s
Proton Torpedo 2200 12 0.4s 15s
Rhazor Missile 2200 20 0.4s 15s

*Rate of fire is the short delay between pulses as the weapon reloads. Recharge time is the longer recharge period after each completed round. The length of delay listed above is the standard rate for each weapon type; some vessels may have longer or shorter delays to reflect their power source, unit type, or technology.