Weapon Reskin Library V2.0

Let’s beam those chickens with these, shall we?

6 Likes

Forgot to add, if the reskin for ion is green, it should make a green hit effect, and same for yellow, while retro should make the same effect as killing ailens.

2 Likes

i love “Ice Boron” and “Wavefrom”, nothing more to say

2 Likes

That’s basically how I imagined it, yeah. (Except retro would be red, of course.)

1 Like

Waveform skin can have low frequency low amplitude for uncharged attack, while the fully charged has high frequency high amplitude.

2 Likes

I like that idea - although, it would put it squarely in the range of skins that required some new programming.

Still, stuff like Mad Painter also falls into that range, so it’s fair game. I like it.

6 Likes

How about some spoons for the Utensil Poker? That would be crazy. :laughing:

5 Likes

Or better yet, screws…

1 Like

AN EXPERIMENT: File Size Estimates for this Library

If you weren’t aware, one of the development goals for CIU is to avoid bloating out the file size for a future mobile port, which throws suggestions such as this into question. Yet lately we’ve been seeing paint options for spaceships get added left, right, and center because they are smaller files (they average roughly 1MB each in CI5).

So I wanted to crunch some numbers and work out how demanding it would be for this library to be implemented. And using CI5 files for reference (which, if anything, might be less optimized than the CIU files) I’ve arrived at some statistics. I have been somewhat conservative with this estimate, and if you have the time to read through the figures you’ll find that there’s probably about a solid 3-9 extra megabytes that you could shave off, depending on how sophisticated the engine’s recolouring abilities are.

If you would like to understand or double-check exactly how I’ve reached these figures (and how generous I’ve been), I’ve included the math below - feel free to take a look:

The Math
  • 3 Ion Blaster Skins x 129KB each = 387KB. Two of these could also likely be done in-software, but I’ll be generous and make them all new sprites to be safe.

  • 3 Neutron Gun Skins x 129KB each = 387KB (Classic Neutron can fit within this file size).

  • Both Ion Blaster and Neutron gun seem to create their collision effects programatically, so I can’t really increase the size anymore here.

  • 2 Laser Cannon Skins x 1000KB each = 2000KB

  • The “Light Cannon” skin is just a super whitened laser cannon - I would be a bit worried if the software couldn’t achieve at least that.

  • 3 Lightning Fryer Skins x 513KB each = 1539KB. Again, two of these are basic recolours, but we’re being really conservative.

  • Laser Cannon and Lightning Fryer use the same file for collision effects. They only take up half that file, but to be safe lets add another three x 257KB each = 771KB

  • 2 Vulcan Chaingun Skins. I don’t know the file size for the rework, so I took the classic vulcan size and quadrupled it to be safe = 2x4x129 = 1032KB.

  • Comet Chaingun just uses a small, whitened comet sprite and a recoloured trail - I don’t think it would need a new sprite.

  • 3 Plasma Rifle Skins x 2 sprites per skin (hitting/not hitting) x 513 each = 3078KB.

  • Plasma handles collisions effects programatically, I believe, so no extra file size there - I’m also assuming that recolouring the AoE effect can be done in-software, too.

  • 2 Boron Railgun Skins. “False Moron” can just use the Boron sprites, and because both Boron and Moron are in the same file, we can actually just shove the two new skins into a single file of identical size. So that’s 513KB.

  • 3 Photon Swarm Skins x 513KB each = 1539KB. All three of these are very basic hue shifts and could easily be done by the software, I suspect, but we’re being cautious.

  • Photon’s weird “glow” effects take up half of a 1MB file. I imagine “photon stingers” as not actually having one of these effects, and you could hypothetically squeeze the other two into the same file, but that’s a super efficient estimate and we’re being conservative. So I’ll add 2000KB (2MB) for these, assuming two files.

  • 3 Positron Stream Skins x 513KB each = 1539KB. You could easily achieve the Magma Stream with basic colour editing, though, and the other two might also be possible with clever layering.

  • Each Positron skin requires another 513KB file for the “glow” effect, but they only take up half that file, and we don’t need to recolour the second sprite in that file, - so we can cram the effects for “Corrupted Negatrons” and “Magma Stream” into just one of these files. “Doom Ray” uses the default purple, so it doesn’t require a second file.

  • 3 Hypergun Skins x 257KB each = 771KB, even though the first two could probably be done by the software.

  • Hypergun currently is efficient and uses photon’s collision effects, but let’s be super wasteful here and give each new skin a unique impact effect instead (which tbh they don’t really need, especially “Intense Focus”). That means three new effects - the original file contains four effects for various weapons, so let’s just round up and add another one of those files - that’s 1000KB.

  • 2 Riddler Skins x 257KB each = 514KB

  • I’m going to assume that the “glow” effect on supercharged bullets can be done by the software using the “additive magic” - so no extra files there

  • Mad Painter needs to be handled programatically because of the way it works - there’s no alternative. Finnaly all three riddler skins use the plain white effect for collision. So there’s no extra stuff needed there.

  • 3 Corn Shotgun (yes, corn shotgun skins. Just because I haven’t posted them doesn’t mean I don’t have sprites) skins at 65KB each = 195KB

  • Let’s add another 195KB under the assumption that each will need a second skin for the WBP popcorn effect, and yet another because I have no idea how the cloud at the nose of the spaceship works and we’re being safe.

  • I have no idea how big the Absolver files are - I have reason to suspect they’re actually pretty small, because the beam is practically created by the software, but just to be super duper safe I’ll slap on an extra megabyte for each skin - that’s 3000KB

  • 3 Utensil Poker skins x 257KB each = 771KB. Superstar Hero really shouldn’t need a new sprite or recolour at all, but just in case.

  • No extra points for collision effects, Utensil skins should all use the default white ones. Likewise I’m pretty sure the software can manage the soft glow on “Superstar Hero” and “Dark Chrome”.

Which leaves the final, conservative, worst-case file size estimate at 21,939KB, or about 22 megabytes.

For reference:

  • The main data file in CIU as of version 46.0 is 335MB large.
  • Each new paintjob is approximately (very approximately, they vary a bit) 1MB large, putting this estimate at roughly 22 paintjobs worth of content.

This means that if this particular library of weapon skins were added in it’s entirety, the main .dat file of Chicken Invaders Universe would increase by no more than 7%.

Whether or not you would consider that a fair trade-off is up to you, and I suppose ultimately up to iA.

Do keep in mind that potentially, depending on the engine’s ability to recolour things, much smaller file sizes could be accomplished, perhaps as small as 15MB, give or take. And these calculations all assume that this specific library of skins were to be added - other, different designs could easily cost even less file size. Another alternative would be to add only one or two skins per weapon, which would allow some of the more difficult to recolour sprites to be cut.

The three questions for thought that come out of this experiment, I believe, are:

  • Is this a reasonable amount of extra file size, or rather, what file size would be acceptable in exchange for preset weapon customizations such as these?

  • How much more could this estimate be reduced by, given the engines capabilities and limitations?

  • Is, ultimately, some selection of weapon skins a viable future concept for Chicken Invaders Universe?

Feel free to use this topic to share thoughts on the matter. :wink:

15 Likes

3 Skins in the base game per weapon and future ones as a separate download (1$/2$ DLC)

The game is worth more than the CHL price, I think that cosmetic DLC may be a good thing

2 Likes

Although I wouldn’t normally consider doing such an extensive cosmetic-only modification during this EA stage (other considerations take priority), this certainly seems to be a popular idea. Some unorganized thoughts:

Paintjobs in CIU are 25% the size of CI5’s.

How would these rekins be applied? You mention per spaceship, but how exactly? If it’s a variation of a weapon equipment (like rarity), you’ll only be able to change a single weapon per mission. Hardpoints? Mission slots?

Are these skins equally valuable/rare? Off the top of my head, the most efficient way to implement this would be to piggy-back them onto rarities (so you get a e.g. common/uncommon/rare/legendary neutron gun), but that would mean (a) some rekins are rarer (hence more valuable?) than others and (b) what I said before, you’d only be able to activate a single one at a time.

Gift colors would probably need to stay the same (the combinatorial logistics of trying to re-color them while also making them sufficiently discrete in all cases would be a nightmare).

14 Likes

The picture I had in my head when I thought about it actually looked something rather similar to the recently added “theme customization” screen, here’s a quick mock-up:


It would be a dedicated submenu. You select the weapon on the left, and then the skin on the right. The display in the middle (optional, but cool) lets you see the weapon in-action, and the slider at the bottom adjusts the firepower level of said example.

This would, like the new “themes”, be a separate menu. Admittedly, it wouldn’t cater to a spaceship-specific approach (that was more of an idealistic scenario, aha) but it would allow for one skin per weapon type to be equipped at any time.

Hardpoints and mission slots would be an issue because you would then have to prevent someone equipping two skins for the same weapon type.

This exact idea also occurred to me - there’s three skins per weapon and three tiers of rarity, so it wouldn’t be too yucky. It seems that, from the feedback I’ve gotten on the actual skins, some are indeed more popular than others and so staggering them with rarities might not be a bad thing, but the point about only being able to equip one skin at a time is still an issue then.

Plus, if they are tied to weapons, where do you then put the description so that people know what skin they’re getting? Replacing the weapon description isn’t ideal, I think.

Personally, I feel like being able to equip multiple skins at once (as in, one per weapon) is more important than having them assigned to specific ships. If someone has an idea as to how both could be accomplished, I’d love to hear it.

Oh yeah, absolutely. I considered making gift artwork at first, and then quickly realized what a problem that would be during gameplay. Plus, keeping default gift colours means you don’t have to re-learn the colours when you buy a skin, and there’s no confusion as to which is which if you buy a few at once.

I may be wrong, but this would be most efficient post Weapon Balance Program, correct? Otherwise that’s four sprites you need to change if you need to adjust one, instead of one.

I’ve held off on a corn shotgun concept for this very reason (although I have made some prototypes for it behind-the-scenes).

Woah, that’s pretty clever. And explains why we’ve been getting so many. :joy:

20 Likes

What if we save weapon skins for an optional paid feature? If we are going to have microtransactions in this game, this feature looks like a very good candidate. From what I know, cosmetic changes that don’t affect the gameplay are pretty popular and reliable source of income in games.

If popcorn shotgun becomes a thing, there is a potential for one very cool skin: Shoots roasted chicken legs when in corn form, and whole roasted chickens in popcorn form. (Even current food sprites could be used for that.)

4 Likes

Had this idea, but no - the “corn” falls back down, so if it looks like food, it will get confused with actual food.
(And it’s not really a corn shotgun anymore than, lol)

4 Likes

Well, corn falls down right now, with normal skin. It doesn’t neccesarily have to fall down in all its skins.

Isn’t this the whole point of weapon skins?

6 Likes

Eh, I guess I’ve got an acid rifle skin, so… :stuck_out_tongue:
Fair enough.

Still, I’ve got some pretty cool ideas that do actually involve corn…

6 Likes

Skins like this are also likely to be very fun. My point was just that they don’t have to be corn related. They can be tho, why not.

6 Likes

Burnt popcorn?

9 Likes

:wink:

2 Likes

This. Micro-transactions would be a horrible idea if you can buy keys with money. Adding weapon skins, some of which are purchasable with keys and others with real money, would be a 2000% better option. Like an optional donation that grants you something purely cosmetic.

8 Likes