#spacell

Remember Loafsprite? It took over the other sprites and is attempting to spread to other sessions, it has already infected over 700 timelines in its host session.I am concerned that someone teleported bread and prototyped it. How the hell do I deal with this situation

Session ID: 220-ψ66C:033-782

- Sorry to be a bother, Dr. Syne Wayve Ph.D, SPaceII Emergency Response Team Lead.

Assuming that you don't ahve access to the kill command, the easiest way for you to do it is to destabilize the Sprite. If you want to avoid destabilizing each Sprite separately, just find the first one to exist and cause that one to spritesplode, the rest of the timelines should retroactively sort themselves out or at least be self-contained.

Toasters and ducks both are good way to destabilize bread-prototyped Sprites.

Sincerely

Report Title: Error displaying Grist totals when in the proximity of flour

Session ID: 220-ψ66C

Details: Apparently, a player loves to bake bread, they even home-mill their flour. You'd think that SGame Systems would be able to handle baking grist, but apparently not. Wayve isn't entirely sure as to the actual origin of this issue. An explanation and a workaround would be appreciated.

- Dr. Grey Aerian, SPaceII Project Lead

Uhhhh, hang on. Oh shit the flour thing.

So basically if you have a bulk material or liquid, each unit (grain, drop, pellet, you get it) is ID'd by the parents unit. That means that if you have flour or sugar, their parent is the box or sack they have been in when the game started. So it's like "This is grain of flour #368889 from This Particular Bag". Because if we had to give an unique number to each grain of flour or snd or drop of water, we'd just give up, let's face it. Nobody likes that big numbers.

Here is where comes the problem from home-milled stuff: It does not have a parent container. When this flour is rendered, the game is too busy with "Oh holy shit, how do I ID all of this even?" to even consider bothering with some build grist, because that's UI element and is therefore secondary.

Fortunately there is an easy solution on your side: Scoop as much of that flour as you can into some bag or box and either via console command or by reapting it clearly and calmly, state that this container is now the parent of all that material. In theory you can assign the room or mill building as the parent of the flour too, since a room is a container, but then you're going to get into big numbers and big numbers make shit slow.

Once a parent node exists, re-assigning children between them is fairly easy (For example: All the water drops you pour into a glass get reassigned to that glass from the tap, and once you drink it and it absorbs in your digestive system it gets reassigned to blood vessels.)

Sincerely

Results: We have set up an automated system in this session to assign flour particles to the container they're in, this is after painstakingly assigning everything else by hand. Ghline expects a memory leak if we implement this system everywhere.

Roadmap: Figure out a more memory efficient solution and patch that into the SPaceII layer of the project.

Closing Remarks: further session observation reveals at least one "Loafsprite", situation is being monitored. Thanks again Gear

- Dr. Grey Aerian, SPaceII Project Lead

You are, uh, welcome.

Sincerely

Report Title: Fatal Error upon launching embedded SPaceI Session

Session ID: 048-χ14A

Details: Session is experiencing an Incipisphere Crash Scenario upon the launch of the SkaiaNet Embedding System that we licensed. We are working on figuring out the stacktrace and would just like a workaround for now.

- Grey Aerian, SPaceII Project Lead.

You don't have basically any Player connected. You need to sacrifice at least one moderately sentient being for this purpose, just send them into the Medium Incipisphere can't be based on vacuum. An avatar would work as a good solution, even upon death the Incipisphere wouldn't crash, because a dead Player is still an existing Player.

Sincerely