FabianK3

BUDDY is a menace.

Small update: Persistent trash is waiting for review and persistent dirt is next on my list.

A great idea and already been mentioned to me a lot. But for any kind of persistent resources, there are some issues to be resolved/discussed/test-merged: What happens if the resource runs out? What if it overflows? Should there be a limit on how much can be added or lost per round? Is there a way or does it need a way to "reset" the resource? - All very highly dependent on the use case. When it comes to the implementation: Not that difficult! Be it a single locker/vendor or items laying all around the ship. The "How" and "When" is more difficult when it comes to persistence imho.

Scream if you love the Nralakk federation

A little update! Notice boards have been put in more places and their new functionality should be now more accessible to each department. (Thanks to @MattAtlas, https://github.com/Aurorastation/Aurora.3/pull/21263). Notice boards also received new sprites: Regular notice boards now can handle a lot more papers. Go fill it to the brim and get scolded for it by your local department head. Additionally, we now have a command board type featuring a command-lock and glass pane for public announcements by command. (This one still has not yet been mapped in, I'll come around to that!) (Thanks to @KingOfThePing, https://github.com/Aurorastation/Aurora.3/pull/21211). Last but not least, persistent trash is nearing completion and persistent dirt is still WIP on my end.

IC statement MSG-CRC: 9e126da28250bdb37077145c0c2b4ac13fb233a4 AUTH-ID: Bradley Knight AUTH-STATE: VERIFIED TIMESTAMP: 15704690275 FROM: Bradley Knight, Atmospheric technician (Heph) TO: Visolela Kuvanga, Chief engineer (SCC) TITLE: RE: Status of propulsion and C-Goliath Drive ----- As per your request, we had another look on the status quo of our current means of propulsion. We used up a pretty big charge with the manual bluespace jump tonight, we are currently capable of three further jumps before we lack the moderator composition to execute any other meaningful jump. Propulsion on the other hand looks good: Phoron supplies are good enough to give us a continuous burn for the next weeks. Ilina, Roebuck and myself went through non-scheduluded maintenance after this mess to keep the thrusters operating at a higher efficiency while we set off away from the hostile cruiser. From the speed we have observed of the cruiser, we should be able to keep it at arms length as long as we don't take any larger breaks anywhere. We are faster, but only marginally in this regard. Concerning your question about next jump availability: We prepared a second charge for the drive that we didn't use up yet this night, meaning we can execute another jump in less then an hour of notice. I would suggest we do. If we set course to CES 146 utilizing a jump, we might get lucky enough for the cruiser to lose partial track - Maybe they are incompetent enough to take a wrong turn, giving us more time. When we made some distance, we also have the time to checkout CES 146, CES 142 and Vela in that direction. Let's look if there is a way out of this infested region in the galactic north. Frustrating thought to be running away from pirates, years ago they would've been the ones running. Where is the SAF when you need them. Let me or the team know if you require any other details from Atmos, Bradley Knight OOC plan Bluespace jump to CES 146, investigate system → burn to CES 142, investigate system → burn to Vela, investigate system → Re-evaluate situation, hope for region exit in the galactic north / utilize remaining resources to evade and move. Edit: Grammer

The moment we face some special conditions for "for this area" / "in this instance" persistence shouldn't be applied, we need to find a generic solution. The issue is for example with filing cabinets, how can a player see that "this" specific filing cabinet is not included in persistence and why is it not included? The moment we come up with arbitrary rules for excluding persistence on some things, things might become obfuscated/confusing quickly. (This is a general problem and not directly derived from the filing cabinet idea.)

and his trusted A last visit in engineering before the shift ends... Oh no! (Oh yeah)

I don't even have context to this myself.

Not quite! But I noticed as well. The PRs should be stay as small as possible to prevent scope creep. Somebody just needs to map in more of them but i think the last discourse in mapping was: Let's wait for the notice board refactoring.

Might be small, but when you also add refillable paper trays, wrapping paper and so on, it suddenly becomes whole new task

Persistent trash - Work in progress https://github.com/Aurorastation/Aurora.3/pull/21217 Refactoring of notice boards and implementation of command notice boards - Work in progress - Thanks to @KingOfThePing https://github.com/Aurorastation/Aurora.3/pull/21211

That is already possible AFAIK. Don't know about the money part though.