# Shortcodes for Component Names

**URL:** <https://aurora4x.com/t/shortcodes-for-component-names/1033>\
**Category:** Suggestions\
**Created:** [August 23, 2026, 7:08pm UTC](https://aurora4x.com/t/shortcodes-for-component-names/1033 "2026-08-23T19:08:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dotu](https://avatars.discourse-cdn.com/v4/letter/d/9de053/32.png) [@dotu](https://aurora4x.com/u/dotu)\
**Post date:** [August 23, 2026, 7:08pm UTC](https://aurora4x.com/t/shortcodes-for-component-names/1033/1 "2026-08-23T19:08:46Z")

</div>

Shortcodes in Component Names.

Right now, default names for components always follow the same scheme, I propose that a tab could be added to the component design window, where this scheme could be changed.

For example the current default for the grav sensor might look like this: “Active Search Sensor AS{As}-R{Res}” the player could then edit this, including shortcodes listed on the tab, covering anything relevant for the component.

Changing the scheme for example to: “Search Radar {As}/{Res} Mk-{AGSS}-{EMS} E-{ECCM}” resulting in “Search Radar 39/100 Mk-28-8 E-2” (AGSS and EMS being the sensor techs’ levels)

And if we wanted to go real crazy with it, the schemes could be exportable/importable from a file or text string as well.

I do realize that this suggestion is rather involved and is purely QOL since what it does can be done manually, though if such a system existed, I’d be very appreciative of it.

---

<div class="post-metadata">

**Author:** ![Marchioness](https://yyz1.discourse-cdn.com/flex011/user_avatar/aurora4x.com/marchioness/32/817_2.png) [@Marchioness](https://aurora4x.com/u/Marchioness)\
**Post date:** [August 23, 2026, 9:19pm UTC](https://aurora4x.com/t/shortcodes-for-component-names/1033/2 "2026-08-23T21:19:50Z")

</div>

I absolutely do this for engines. Engines by default just list type and EP production. However, there is so much more necessary to know about engines.

As an example, if I made a Nuclear Gas Core Engine, I will append a model number to it with values rounded or truncated, multiplied by 10, or whatever it takes to make them whole numbers: Engine power-size-power modifier-fuel efficiency-thermal output

Rolls-Royce NGCE E87-1-250-7-100

That would be a 50 ton fighter engine with 87 (and probably some fraction) power output, size 1, power multiplier of 250, fuel efficiency of 0.7, and 100% thermal output. (numbers drawn from top of my head as I am not in Aurora right now)

This makes my engine designs very similar to real world jet engines like the Pratt & Whitney F100-PW-200, which powered the F-16.

The point is, of course, to distinct engine generations and types from each other. I might have a nearly identical engine that has better fuel efficiency or a significantly reduced signature for stealth ops. I may also have some very old engine with similar output to a newer engine that is half the size and 1/4 the fuel cost.

---

<div class="post-metadata">

**Author:** ![nakorkren](https://avatars.discourse-cdn.com/v4/letter/n/b487fb/32.png) [@nakorkren](https://aurora4x.com/u/nakorkren)\
**Post date:** [August 23, 2026, 11:42pm UTC](https://aurora4x.com/t/shortcodes-for-component-names/1033/3 "2026-08-23T23:42:30Z")

</div>

I would love the ability to code the naming convention for components. I do it manually right now, which works, but it would definitely save lots of time for anyone who RPs or has their personal preferred nomenclature.