Have people tried this theory? If so, Gif of it being used.

I got it.
I know what to do

you have to use 2 objects,

the first object, has a sprite, and autogenerate = 1
then it somehow switches to a new object, such as a gib (IE while in the inventory, the object gibs after a lifetime of 1, and the gib is still equip-able. since objects can gib/emit while in the inventory)

The second object, has the atomgroup as the 'parent object' (I saw the code a few times but I dont remember where, or if its still in game, then again, it might have been a different game >_> )
but still have Autogenerate = 0 (so it uses the atomgroup as the previous object, but has a new sprite, THEN doesn't autogenerate the new sprite.

Someone test this, my comp can't run CC, it needs
fixed, i have like 110 MB of ram.


//edit//
If this needs to be an attatchable such as the helmets and armor on the new clones, this wont work, because if it gibs, it will detatch from the actor, it might work with guns/shields/grenades though.

also, with how sprites are numbered 0000-9999, maybe you could glitch the file-names so that it uses sprite 0, but bases the atomgroup off of, i dunno, -1?

ALSO, new idea,
2 sprites, sprite 1 - has a sprite for the shape/atomgroup, and autogenerate = 1, then it forces it to always use sprite 2, which is autogenerate = 0 and is blank. if you can't do that, it would still always exist but it would flicker in and out (IE you can see it on every other frame, but it always acts as being there, like some glitchy sega genesis transparancy effect)

Couldn't you just do it manually?

Manually making atomgroups is a PAIN.

Well, in this case I think it's the only option.
And certainly the best option if nothing else.

If Alenth is correct, then you could do it like this:

Define a VISIBLE shield. Use the sprite filepath, give it the materials, AutoGenerate = 1. Make it so that it is NOT buyable, however.

Now make a CopyOf. Give it a new sprite (Base.rte/Null.bmp) but don't redefine any material or atomgroup code. Give it a new instancename and make it buyable, however.

If it's possible, that should do it, right?

I don't really see why not, some of this nonsense makes about as much sense as a sunbathing melon dipped in melted platinum.

Yeah, I do recall that notice in the old engines...
...
// Have to restate atom groups otherwise they won't match the new sprite


But, I tried to make the invisible shield by making use of this, and it did not work.

Damn, manual must be the only way then...

I also tried manual atomgroups; this made the shield not get hit by anything, it couldn't be picked up, but it interacted with terrain correctly when dropped.

õ_o

Ok, I don't think it can be done.
Unless, the atomgroup wasn't thick enough to collide properly, because sometimes when you shoot super-thin objects your bullets pass through it.

after reading all of this, i think i have a functioning answer that isn't gibberish

make a shield that works normally and has a sprite.
make it autogenerate = 1 (visible sprite)
buyable = 0

new instance, copy of THAT,
new sprite (invisible)
autogenerate = 0
(do not generate a new atom group based on the sprite, use the old one, from the prior object)

if your not sure on the shape, attach glow effects to the edges of the shape where it *should* be, and tweek the unused sprite from there. you will have to include both.

That's been discussed and tried.

It didn't work.

Yeah ah.

You forgot deepgroup.