Hello there, i build a map with some scripted pelicans crossing every 60 seconds, which worked really fine. Then someone said "perhaps they spawn a little too often". So after doing some other changes on the map, i touched those pelicans. But touching them kinda crashed them completley. So i had to rebuild them from 0. Now it seems like everytime i place a pelican, it has some hidden scripts. If i start a custom game, they start moving - without scripts. When i go back into forge, 2 out of 3 pelicans are just...gone...? Can someone help me? The last save with working pelicans is way too old. And i dont wanna miss them, because they were awesome ._.
If you have the waypoint link to your map file, maybe someone can figure it out. I might be able to look into it, but I can't promise I won't disappear for weeks.
Youre right, here is the link: https://www.halowaypoint.com/de-de/...Mittmann_cc128257-dcee-4ea5-b5a5-6c7a45768394 But i dont remember...i guess right now i deleted all pelicans. So you probably have to place new ones... Thanks!
This currently is a huge problem with Forge. Script counts in the budget will not always decrease when you delete them. But the number will increase when you ad scripting. Scripted objects now have a tendency to pass on scripts to other objects randomly. And it can't really be stopped. If you delete the object a script has passed to, the script will just move to another object. I have had this problem a number of tomes where I had an object set to despawn at the start of a match. Everything worked fine until the next time I loaded the map hours later and that script had passed to parts of a building. I tried everything, but I couldn't get it to stop. I ended up havibg to go back to an older copy of the map that had no scripting at all. My recommendation is to try and avoid scripting for the time being if possible. It can really screw up your map.
Yeah, the whole reason I joined Forge Hub a couple of weeks ago was to see if anyone had solutions to all of these scripting issues. Everyone is having a problem, but no one had a solution. I was really hoping that today's release would come with some bug fixes, but it didn't. Looks like we'll have to wait a whole month to see if anything at all will happen.
Good to know i'm not the only one But it seems like it works now. Just let the map some days untouched...