[DONE][Suggestion] Image options for the Ufopaedia and armors

[Alex_D]

I'd like to suggest two features:

1. Currently the image option for a "type_id: 5" pedia article (armor) is the inventory_image of the armor. There is no other option. Adding "image_id" to this type of article doesn't do anything. I'd like to propose an alternate image option (either regular, bigbos, or CPAL) that would replace the inventory image of the armor if specified. If not specified, things remain as usual.

The reason is maybe sometimes one may want to create a special image for the armor than just the inventory image. If it's too complicated, is there a template for the type 5's like in "BACK08.SCR" that we can use?

2. Kind of related to above. The game will look for the pedia article based on the string of the armor. I'd like to propose a default article to be added under "armors:" (e.g. "alternate_pedia: STR_MY_FAMILY_OF_ARMORS") that the game will look for if specified. If not things remain as usual.

Same reason as #1, maybe we have created several types of armors that only differ from each other on the image and this way we could reduce clutter in the ufopaedia.


All of these suggestions came to my mind after checking the "Xeno Ops" mod and its approach to multiple armors. There is no MMB linking to the pedia article in that mod.

If there is a similar solution in ruleset commands that will give the two features requested, I'd like to know them.

[Meridian]

1. Currently the image option for a "type_id: 5" pedia article (armor) is the inventory_image of the armor. There is no other option. Adding "image_id" to this type of article doesn't do anything. I'd like to propose an alternate image option (either regular, bigbos, or CPAL) that would replace the inventory image of the armor if specified. If not specified, things remain as usual.

The reason is maybe sometimes one may want to create a special image for the armor than just the inventory image. If it's too complicated, is there a template for the type 5's like in "BACK08.SCR" that we can use?

1/ done, for both standard palette and custom palette

custom palette info: https://openxcom.org/forum/index.php/topic,4957.0.html

[Solarius Scorch]

I think what Alex means is something I've encountered myself in XCF as a sort of issue. A common example is two gender versions of enemies (like male and female Pioneers, or male and female Tough People in Piratez). These two need two units, two armours, and two items, so also I need to make two separate armour entries (even if the mechanical values are exactly the same). It would be nice to have just one Pedia entry, showing both paperdolls or something.
Not a big deal, but still.

[Meridian]

It would be nice to have just one Pedia entry, showing both paperdolls or something.

You mean one Pedia entry, showing the SAME paperdoll, right?

Like Male Pioneer and Female Pioneer would point to the exactly same ufopedia article, showing the same paperdoll, same stats, same everything.

[Alex_D]

1/ done, for both standard palette and custom palette

custom palette info: https://openxcom.org/forum/index.php/topic,4957.0.html

2/ I don't understand how that is supposed to reduce clutter in Ufopedia... you still need to create separate Ufopedia entries because of different images. Please clarify.

1. Thank you!

2. The clutter part was an idea of a possible benefit. Some mods (*cough* Piratez *cough*) have an armor for multiple soldier types (gal, other gal, yet another gal) and for multiple environments (land, sea, space) are essentially the same (in stats anyways). These multiple entries, could be reduced to only one (plus a bit of reworked text) to refer to a single type of armor. Like "storeItem" but for armors.

EDIT: Yes, what Solarius said.

[Meridian]

2/ added

Example:

Code: [Select]

armors:
  - type: STR_PERSONAL_ARMOR_UC
    ufopediaType: STR_SKYRANGER
  - type: STR_POWER_SUIT_UC
    ufopediaType: STR_SKYRANGER
  - type: STR_FLYING_SUIT_UC
    ufopediaType: STR_SKYRANGER

Please note that unless the armors are identical, the Stats for Nerds will be lying to the player.
You've been warned.

[Solarius Scorch]

You mean one Pedia entry, showing the SAME paperdoll, right?

Like Male Pioneer and Female Pioneer would point to the exactly same ufopedia article, showing the same paperdoll, same stats, same everything.

Basically yes. I would like to see both pictures there (female and male), but technically it's just one article.

[Yankes]

Maybe option for multi page article that change only graphic for each variant?

[Solarius Scorch]

It appears that the ufopediaType command doesn't extend to the display on this screen:



That armour is set up to use this Pedia page instead:



Should I add this string (duplicate "Muton Combat Analysis")? Or should the feature also update this description?

[Meridian]

I'll check...

[Meridian]

It appears that the ufopediaType command doesn't extend to the display on this screen:

Yes, `ufopediaType` only says which pedia article will be opened on M-click.
It doesn't rename the armor.

Should I add this string ?

Yes.

(duplicate "Muton Combat Analysis")?

Actually, I would prefer to see the correct armor description there, e.g. "Muton Engineer Armor".
The pedia article title and the armor name don't have to be the same.

Or should the feature also update this description?

No.

[Solarius Scorch]

Thank you, that clears this up.

[Buscher]

Hi,

is it possible to extend this feature to items: ?

I have a few items that are pretty much a reskin. These items cannot be loaded on your craft and are for selling only (Chaos vs Sanctioned items). For the battle relevant stats they are the same. If not I can live with creating duplicate articles inside another section.

Thanks.

[Meridian]

ok

[Meridian]

added in OXCE 7.8.19

Example:

Code: [Select]

items:
  - type: STR_PISTOL
    ufopediaType: STR_GRENADE
  - type: STR_RIFLE
    ufopediaType: STR_GRENADE
  - type: STR_LASER_RIFLE
    ufopediaType: STR_GRENADE

Please note that unless the items are identical, the Stats for Nerds will be lying to the player.
You've been warned.