attached movers

[MrC]

i am working on a map and for some reason, without a game mod for example the mover and attached lights work.
but with jcoopz / prototype, the light does not work.
any ideas?

[Krull0r]

Sry no idea. But you can try one thing.

Select your attached light in the editor. Move it one unit and back and save your map without rebuilding lights.

[[]KAOS[]Casey]

jcoopz and a jcoopz... prototype? or is there another gametype called "prototype"

[BobIsUnreal]

prototype?"

aka "ugoldmp"

[[]KAOS[]Casey]

So when this issue occurs, you're only running the gametype(s) and no mutators, etc? offline testing?

[MrC]

yes, seems to work in normal coop

[MrC]

figured out a way to do it.
seems normal lights wont work, instead flashlightbeam does work with
movers.

[[]KAOS[]Casey]

If you're really running no mutators and just those, makes me wonder..

my first thought was some insanity with dzmapm since jcoopz internally runs something similar iirc

[Masterkent]

Lights whose bNoDelete is true or bStatic is true determine the static lighting on the map and are not supposed to move in the first place. Comparing different Coop game types doesn't make any sense here, because when such lights are dynamically moved to other place, a sane behavior is not guaranteed even in a single-player game. Setting both bNoDelete and bStatic to false for an actor whose type is Engine.Light won't let it reliably appear on clients in network game, because a client can remove it and won't be able to spawn again due to default.bStatic being true. A movable light must have bStatic and bNoDelete set to false and be of class type whose defaults for bStatic and bNoDelete are set to false.

[MrC]

that makes sense what you mentioned mk. the defaults for the regular lights are set to true. the flashlightbeam defaults are set to false, so that
explains why it works. i was just following the tutorials from
TheCompleteUnrealEdReferenceGuide.chm ... sorry for my mistake of not knowing this and sorry for bringing up jcoopz or prototype.