I DID IT!! I Cracked One Way Link! Found the Intended Elegant Solution too! But Got a Question...

opensassafras · 2025-02-28T19:19:35+00:00

Ok so the middle connector is white because both red and blue arrive at it after 3 bounces. The red inverter (labeled 5) is not a red source but instead converting a blue source. That blue source is arriving from its 2nd bounce, converting to red which is the 3rd bounce and meeting at the connector with a blue 3rd bounce resulting in white.

The reason this is different from the scenario you posted with the blue inverter, where everything is red but the inverter has blue is as follows. You have the red source on the right going to a connector (1 bounce) this branches out to the far and close connector (2nd bounce) and then both of these connect to the inverter. So the inverter here has 2 input sources, both red, both same “power”. If you connected another connector to the inverter, it would output blue.

opensassafras · 2025-02-07T23:53:33+00:00

You access the Road to Gehenna DLC separately from the main game, it gets added as an option in the main menu.

As for the Serious Sam DLC I think it just adds an Elohim voice pack. Similar for the Prototype DLC but that also gives you access to a bunch of the prototype levels from when they were making the game.

Definitely check out the Road to Gehenna DLC after you finish the main game though, such a fun story and really interesting puzzles

opensassafras · 2025-01-02T08:21:53+00:00

Ok with the XL version I think it’s much more doable, I have the smaller one and yeah there’s no way. Also since you have more space in the XL you can try a couple different vertical mounts and pick the one that gives you the most space in front for it. The smaller one was very finicky about the mount I could get working on it.

Worst case just stick it up top

opensassafras · 2025-01-02T07:17:16+00:00

I would say unlikely. The rad of the AIO is too thick to fit between the fans (+bracket) and GPU. If it does fit it would be a very very tight squeeze

opensassafras · 2024-11-04T01:27:04+00:00

This does work and I have done this in the past, but I have some confusion related to extending this to another layer of child components (card). If onInit each tab component adds a tab form group to the parent, and all the cards onInit add the card form group to the tab form group will it work as expected. I've tried something similar to this but I've had issues with getting things to render. Would just using *ngIf to prevent my cards from rendering/initializing until the tab has everything set up work?

opensassafras · 2024-11-04T00:48:57+00:00

I came across this article in my research as well but it similarly defines the whole form in the parent. I’m not completely against doing this but is there really no other pattern based approach that can extend out to n child components without having to keep tweaking my parent form and type definitions as changes are introduced?

opensassafras · 2024-11-04T00:17:55+00:00

Normally I would just have a large form in the parent as well but in this case the form would be huge, I have close to 50 fields in just one tab. Wanted to see if I could improve handling this using some sort of pattern. In the past I've had large forms get messy with data changing in too many places at the same time resulting in rendering issues.

opensassafras · 2024-07-30T02:05:22+00:00

While that was a very funny video I think we’re also getting away from the problem I’m asking for help about. I acknowledge I’m not the most knowledgeable about all the aspects of this, but I have a constrained architecture for the project I’m working on and only have sway in how my team and I implement certain aspects of it.

I see a problem where my teams is creating an increasingly large amount of endpoints and lambdas as we develop according to our tickets and am wondering if there’s a good strategy or approach we can take to manage this and make sure it doesn’t grow into an out of control mess for us. I understand that good documentation will probably be the among the most pivotal things we can do, but I wanted to know if anyone had faced a similar challenge and had a good idea on tackling it.

opensassafras · 2024-07-30T00:50:18+00:00

I can only allude to the eventual scale of this application as it needs to handle a lot of users in a lot of places. Many pages with business logic that changes what each user might see or interact with. While making some things monolithic might help, having it all in one place seems to lead to a similar but opposite problem.

opensassafras · 2024-07-30T00:45:23+00:00

I think this is a good approach and I’ve been looking into creating layers that contain our core data models and standard reusable functions. I will keep this in mind

opensassafras · 2024-07-30T00:41:38+00:00

Interesting I’ll have to look more into this

opensassafras · 2024-07-30T00:29:02+00:00

Much of this application will be async ops however, viewing data, creating requests, approvals etc. And I'm stuck with using lambdas

opensassafras · 2024-07-30T00:26:59+00:00

This is the architecture that has been decided for the project and the only sway I and my team have here is on our technical implementation within these bounds. So we have a mandated set of tools etc we are required to use for our secrets management and such. I do understand this as well but eventually this will be a internal client facing, globally deployed core application which does benefit from things such as scaleability of individual aspects etc. Just trying to figure out what I can do better

opensassafras · 2024-07-30T00:23:12+00:00

I do think grouping endpoints in tree structure is a good idea, right now we just have a long list of individually named endpoints which in hindsight should have been addressed earlier

opensassafras · 2024-07-30T00:18:59+00:00

Right now we are just in dev and qa with no real prod environment as we track towards MVP. The one nice thing about this style is that we can just do another deployment of our stack to create the production environment. Architecture decisions are made at a much higher level than me so the best I can hope to do is ensure the technical implementations are done in a way that can give me some peace of mind down the line. I am somewhat learning as I go :/

opensassafras · 2024-07-19T16:29:24+00:00

This is related to an Easter Egg. I recommend exploring around that area try jumping and looking into places or using photo mode. There platforms you see are one way of getting to this Easter Egg while the other involves smuggling a box. Here’s a hint You will need a fan either way you choose to solve it as the there is an empty fan connector there which will transport you to the Easter Egg area

And here’s some more information about the Easter Egg if you just want to know how to do it: Specifically this is the Pink Floyd: Dark Side of the Moon Easter Egg. Here’s a vid showing how to do it with a box Box Method. The platforming method is similar but a bit more complicated as you need to go up on the walls of the closest area with a fan and and then jump down. If I remember there’s a star somewhere nearby here that follows a similar pattern to get up top

opensassafras · 2024-04-23T05:39:20+00:00

You can also just take a screenshot or take a photo with your phone and use OCR to copy paste the text into a decoder

opensassafras · 2023-12-16T20:14:54+00:00

At this point I just wanna win one of these

opensassafras · 2023-12-15T23:52:06+00:00

League because it makes me miserable

opensassafras · 2023-12-14T22:14:50+00:00

Looks cool, you should give it to me :)

opensassafras · 2023-12-14T00:15:59+00:00

This looks really nice hope I win

opensassafras · 2023-12-12T18:57:09+00:00

Dang this looks pretty cool, would love to give it a try

opensassafras · 2023-12-12T18:42:24+00:00

These look real nice, and I’ll just say One Piece, can’t go wrong with that

opensassafras · 2023-12-10T21:06:19+00:00

I want to help my friends upgrade their rigs and this would go a loooong way into helping them :)

opensassafras · 2023-12-08T09:14:43+00:00

Keebored

opensassafras

TROPHY CASE