UPDATE (3/19/20): Just a quick note regarding the team at Klei Entertainment. As noted previously, everybody at Klei Entertainment is working from home due to the Covid-19 outbreak. Many of us have been working especially hard to help maintain operations as we all move out of the office and into our homes and with everything being done online, extra time must be spent in organizing conversations and trying to maintain communication. As some of you may know, we have a very open office and we are almost always in contact with each other as we go about our days. Some of us work across multiple teams and that work has become a bit more challenging for everybody. That being said, at this time the transition has not caused any major disruption in our operations, but it would be overly optimistic to expect that we won't have any delays at all. We're going to have to be especially mindful about this in the coming weeks and make sure we don't take on too much work so we can keep things running smoothly. We will let you know as we see how these changes affect our timelines. Thanks UPDATE (3/10/20):
The test yesterday went well. We got the whole office (mostly) to work from home without significant issue. As a result, Klei Staff that can work from home have been asked to do so until further notice. This means that we will have to cancel the Rhymes with Play stream until we are all back in the office. This shouldn't affect anything else at least in the short term, but if things change I will update you all here. Original Post: Hey everybody, This Tuesday March 10th, 2020 the entire staff at Klei will be working remotely for 1 day in an effort to prepare the studio to work remotely for a little while if the need arises. Klei is already set up pretty well to allow for working remotely, however we are going to have a one day "dry run" with the whole studio so that we can identify and avoid any issues or downtime that may arise should choose to implement a work from home policy due to COVID-19 outbreak concerns. Unfortunately this does mean that we will be canceling the “Rhymes with Play” Art stream this coming Tuesday, however unless the situation changes we expect everything at the studio to be back to normal Wednesday and we’ll continue our regular stream schedule Thursday March 12th. If the situation changes at all, we'll let you know. Thanks for your understanding.
Search the Community
Showing results for tags 'ribbon'.
Found 1 result
Not too long ago (see link below) the issue about a missing reset port on the counter was raised and the devs quickly added it to the device. Just a while back, on the livestream another player suggested that the counter should also count backwards. It was even added before the preview went live. These reactions are phenomenal, but i am afraid that we are not with the counter done yet. And frankly, the endresult of a 1x3 counter does not quite feel oni-ish as well, because most automation buildings are alot smaller than that. 1x2 just felt the right size. My use-case: i am using an isolated living area for 32 dupes. Whenever my dupes leave that living area, they have to use one of my 32 exo-suit docks. For several reasons (modulization, space constraints, etc.) i have opted to go with 4 8-dock entrances for my dupes. This feels like a good trade-off to me, because i'd imagine that my dupes would simply enter from where they are coming in and leave to where they want to go. The problem is that only 8 dupes can leave from every exit. This is a reasonable contraint and i could even add additional docks to aleviate that issue. However the problem is when the dupes want to enter my living area. For the first 8 dupes, everything is fine, but as soon as the 9th dupe enters, his exosuit will be dropped to the ground, forcing me to manually find the unoccupied dock of the other 24 and order a dupe to supply the exosuit back to the original entrance. To workaround this issue, i have restricted access to every of my entrances to only 8 dupes. This neglects them from choosing their optimal entrance and even when only 4 of my 8 dupes who are assigned to one entrance/exit have left my area, nobody else will be allowed to use the ports, leaving 4 suits on that entrance/exit vacant. My hope was that someday (tm) i would be able to do an automation that would restrict access to my entrance/exit based on how many dupes have passed in each direction. Something like *gasp* counter. By now you might have already caught on to my problem. One direction is fairly simple: install pressure pad, install counter, wait for dupes to pass, done! But that is only the counter in one direction of the passage. To correctly count how many docks are currently vacant, i would have to increment for every dupe, who leaves and decrement for every dupe who enters. Ofc, i could simply add 2 counters, match their ribbon wire output, if it is even, reset both counters and work some other logic magic to extract the correct number of vacant docks on a third counter. But i would opt for a better counter interface. My suggestion: The counter should have 3 inputs (bear with me, erika, you wont have to make a 1x4 counter). One input to increment, one to decrement and one to reset. And of course the ribbon output of the currently displayed number. It should also keep the checkbox to choose whether the counter should mainly count up or down (effectively swapping input-1 and input-2). But i would also like to bundle all this functionality in a ribbon wire input. This would allow the counter to still be 1x2, it would add an additional incitement to use ribbon wires, it would still leave us with 1 unused input port for future use and it would allow us for a blueprint of automation tech progression. The out-of-the-box counter should come with the build-flag (from the livestream), outputport (livestream) and single-input (increment/decrement based on flag). As soon as ribbon wires are researched, the single input wire will still have the same functionality, but it is also possible to use a ribbon wire as input, allowing us to decrement (or increment depending on build-flag) and reset. As already suggested, this blueprint could be applied to other buildings with automation-ports as well, further integrating the ribbon with the oxygen prison. Examples: rocket out: ready potentially: ready, fueled, manned in: start potentially: start, request astronaut battery out: sufficiently full sufficiently full, full, empty pipe sensors: element/temperature/mass matched matched, no measureable value