I have a map problem with the 2nd version of my map (ejk_hq2 aka ffa_ejk). The NPCs in our map spawn, but invisibly. If u try to ride the spawned vehicles, jk3 crashes. The NPC bots spawn invisibly and still do dmg. We tried redoing the triggers and still was the same... Any ideas?
I just noticed that the rancors i nthe map that were set to spawn when map started, do work. Also the bomber (ship) in our map works, however u cannot fire the bomber, and the bomber respawns with the same problem.
is the map for sp or for mp? maybe u did something wrong with entities
ffa_ejk
MP
Yeah as Meush pointed out, it is for MP. If anyone can figure this one out we would be most greatful. Weve had this map on hold for 4 weeks trying to figure it out. Since we couldnt, we went to the gamingforums JK3 community... Im sure someone out there knows our problem.
Cmon, someone knows
Did bomber could fire *ever*?
I mean was there a moment (some compile) when bomber could fire?
If yes, check what was bad. Delete this bomber, make it once again
If not, check .npc and .veh file
It could fire but the bomber isnt the main problem. ALL the NPC's are malfuntioning, even when i spawn them from an rcon command they dont work.
Ok i figured out the problem. Just dont no how to fix it. Every NPC in the map multiplies, idk how it does but it does. Ex, if i spawn from a button a speeder, it shows one spawned, but if u do NPC kill all repeatedly, it shows that it is still alive for another 10-15 times........... dunno why. An interesting one is one of the speeders has a bomb in the back that fires. Normally its just one thing that spawns then blows up, but with this bug, the bomb repeats about 15 times also............................................ So bascially, all the NPC's seem to spawn multipule times in the memory or something, even tho it spawns only once in visiion. Any ideas how to fix?
Erm...re-do the tutorial, you've got it spawning multiple times which has to be due to an error on your part. Maybe it's something to do with the NPC entity or maybe it's something to do with your button.