Author Topic: Creating an artificial MainBrickgroup object without it being destroyed?  (Read 864 times)

I have a server which must load bricks via an artificial method. As such, I want to be able to create my own MainBrickgroup object when I start to load these bricks. However, if I do this, it always gets overwritten when the first client joins the server.

//Methodology:
if(!isObject(MainBrickgroup)) new SimSet(MainBrickgroup);
MainBrickgroup.add(new SimSet(Brickgroup_11239));

//The artificially created MainBrickgroup gets destroyed when someone joins the server.



Is there a way to create the MainBrickgroup object before someone joins without it then being destroyed when someone does join?

Why are you trying to create your own main brick group?

Why are you trying to create your own main brick group?

I have a server which must load bricks via an artificial method. As such, I want to be able to create my own MainBrickgroup object when I start to load these bricks.

Why do you always go into help threads just to be unhelpful?

I have a server which must load bricks via an artificial method. As such, I want to be able to create my own MainBrickgroup object when I start to load these bricks. However, if I do this, it always gets overwritten when the first client joins the server.

Are you sure that it gets overwritten when the first client joins the server and not when all add-ons have finished loading? That is the case for the mission group, mission cleanup and several other global server "groups". There is no need to start loading a save the instant your add-on executes; wait for the next frame of the server/client with a schedule time of 0.

Why do you always go into help threads just to be unhelpful?

...

Are you sure that it gets overwritten when the first client joins the server and not when all add-ons have finished loading? That is the case for the mission group, mission cleanup and several other global server "groups". There is no need to start loading a save the instant your add-on executes; wait for the next frame of the server/client with a schedule time of 0.

Hmm, I hadn't even considered that. I retract my insult.

I retract my insult.
I don't think you can do that...

On the subject, port may act like a douche sometimes but he almost always has a valid point, just be sure that you're not reading between the wrong lines

just be sure that you're not reading between the wrong lines.
line.*

Why are you trying to create your own main brick group?


I actually don't understand in the least why you would want to create the MainBrickGroup yourself. Why can't you just use the default one? It's not like you gain anything by instantiating it yourself.

What's the end goal here?