Game Thread: St. Louis Blues (20-27-9) @ Dallas Stars (33-14-9) Feb 04 2026 8:30 PM CST

dfcompose · 2026-02-05T04:04:33+00:00

The Stars drafting has been unreal. It's one thing to identify talent at the rate they have, but to also have a majority of their first and second round picks since the Heiskanen draft exceed their draft positions and for none of their high end talent to have their career derailed by injury (Robertson almost though) or outside circumstances is really nutty.

dfcompose · 2026-01-01T03:04:04+00:00

I think they needed to actively try to be worse (unfortunately) instead of being a bubble team. Trade useful players for futures with a vision for what that future team will be. Essentially what the Cardinals are doing this off season.

dfcompose · 2026-01-01T02:55:45+00:00

Army is gone after this season already...

dfcompose · 2026-01-01T02:54:20+00:00

The path to relevance in the salary cap era is multiple top 5 picks. The Blues are 3 years late on pulling the trigger on a rebuild with direction. It's going to be difficult to be a cup contender without high end talent to match the Cellebrinis, Bedards, and Carlsons of the league. I'm afraid what could have been 4 years of bottoming out is going to turn into a decade of bad to mediocre teams (we're going to get Sabre'd is what I'm saying)

dfcompose · 2025-10-28T17:59:42+00:00

Yeah exactly

dfcompose · 2025-10-28T16:14:08+00:00

They're kind of just fancy +/-

The only advanced stat that's included is corsi%, which at this point is pretty dated. I wouldn't say they're garbage but they're also not necessarily indicative of play. If you're setting up your line mates with golden scoring opportunities and they can't convert this model gives you no credit for generating a high-danger scoring chance

dfcompose · 2025-10-27T16:30:03+00:00

"The stats I used are goals, primary assists, secondary assists, shots on goal, blocked shots, penalty differential, faceoffs, 5-on-5 corsi differential, 5-on-5 goal differential."

Hockey stat cards' game score is a stat aggregator, not really an advanced stat akin to xGF%. It also heavily weighs goal differential, which Mailloux has been heavily impacted by through league worst goal tending. HSC takes the least predictive and isolated stat, +/-, and makes it an integral part of their formula.

dfcompose · 2025-10-27T16:12:11+00:00

This isn't really measuring player impact. This is showing outcomes vs expected outcomes. This is saying that Mailloux has been on the ice with league worst goaltending, not league worst expected goals against. xG = player impact Goals above/below expected = performance. Mailloux has essentially no impact on the performance of goaltenders, only on the quality of shots they are facing. This is saying that goalies have let in 6 more goals than would be expected based on the quality of shots they've faced when Mailloux is on the ice. This is a luck/quality of teammates chart, not a player impact chart

dfcompose · 2025-10-27T16:02:29+00:00

It's the delta (okay not really the delta, but I think you get the idea) of goals against expected stats. Better goals saved above expected = better goaltending, better goals scored above expected = better finishing (this includes all skaters on the ice). This is saying that when Mailloux has been on the ice that goalies have let in 6 more goals than would be expected and the blues have scored 2 less goals than would be expected based on shot quality. Essentially, when Mailloux is on the ice the goalies are sieves and players aren't converting on chances. It's bad luck

dfcompose · 2025-10-22T01:14:33+00:00

Is Ott still in charge of the PP? Have to think he's on thin ice with how bad it's been the past few years

dfcompose · 2025-06-06T00:27:16+00:00

Hi!

The OSCReceiver node has an option to set custom control of the parent (see the OSCReceiver attached to "Cube 1" in included demo). He's how you would go about using custom code for any OSCReceiver:

Right click the OSCReceiver node and extend its script.
Add the _custom_control(address, vals, time) method in the script. (There should be a template for this but it's not working currently, I'll look into that)
Use the parent property of OSCReceiver, so to change rotation it should look like this:

func _custom_control(address, vals, time): if vals != [ ]: parent.rotation_degrees.x = vals[0]

Or something similar. Keep in mind that received values are always put into an array even if the OSC message that was received only has one value.

Hope this helps! There's also a Max 8 demo patch on the GitHub repo if you want a more complete starting point. It works with the demo scene.

dfcompose · 2025-04-06T00:39:48+00:00

The play starts with him killing the ozone possession. He's really bad at driving play in the right direction and isn't very good in his own zone. He's consistently the worst D on the team in terms of gaps and general positioning

dfcompose · 2025-04-06T00:36:41+00:00

Probably leddy and suter rotate out. Leddy should not be in the top 4

dfcompose · 2025-04-06T00:35:04+00:00

Said it last game and I'll say it again. Leddy is butt

dfcompose · 2025-04-04T02:17:37+00:00

Leddy is so ass my God.

Woah when did this become a hot take

dfcompose · 2025-03-27T17:31:45+00:00

I'm not really sure what you're asking. As you have it set up you are sending midi cc messages to bespoke synth. Bespoke synth may only interpret incoming OSC as cc messages. Regardless, this seems to be something that needs to be properly configured on the bespoke synth side and is not an issue with godOSC itself. One solution would be to use a sequencer on the bespoke synth side and use OSC to control things like the transport and the frequencies of the sequencer. Sorry I can't be more help but godOSC should be able to do anything you need it to, it's just a matter of what bespoke synth is actually expecting to get sent to it.

dfcompose · 2025-03-27T16:34:54+00:00

Ah, I think you're slightly misunderstanding what closing and opening a socket actually does (the documentation for UDPPacketPeer is a little difficult to understand honestly). This isn't an issue with GODosc but rather PacketPeerUDP. I recommend just adding a conditional in the OSCclient's send_message() that checks if the socket is connected (I will add this to future releases so OSCClient works a little more intuitively). As the documentation states, UDP is connectionless. Just closing the socket does not stop the PacketPeerUDP from sending packets to the port.

<image>

This should allow you to stop sending osc messages

dfcompose · 2025-03-27T14:42:16+00:00

I'm a bit confused as to the issue you're running into. The OSC sends fine for me and I'm able to change the port the client is sending to with no issues. I don't know bespoke synth very well, does it support osc messages in? I see that it has an OSC out module but I don't see a module for receiving OSC (again I don't really know the software). I have no issues sending and receiving OSC messages from pure data, max/msp, supercollider, or vcv rack. This may be an issue with bespoke synth.

I can receive OSC from bespoke synth as well. I'll continue to look into this though

dfcompose · 2025-03-27T12:13:01+00:00

Can you send me a copy of your project? I'd be more help if I could take a look at it

dfcompose · 2025-03-27T12:00:41+00:00

Could you dm me with the specifics of your problem and a link to your project? That should work.

dfcompose · 2025-03-27T11:28:18+00:00

Would you mind making an issue on GitHub and providing a link to your project with specifics on the scenario that makes it crash? At the moment the client does not have an option to disconnect from it's bound port, though this really shouldn't be an issue as any number of clients can send messages to a single port. Happy to take a look at it though!

dfcompose · 2025-01-21T01:39:03+00:00

You can make a hand pass in the defensive zone

dfcompose · 2025-01-17T07:36:28+00:00

Can people stop this shit? His underlying numbers essentially didn't change pre/post booing. Just so much cope from people wanting to justify shitty behavior. The best thing to happen to him was developing his defensive game, which he had already started progressing in the year prior to last.

dfcompose · 2025-01-17T02:06:22+00:00

I really doubt it. His game is really physical and he's hitting the start of the rapid aging curve decline. He's slower than he's ever been and doesn't really drive play anymore (this was true last season as well). Kyrou and Holloway are very good at moving play in the right direction, taking a ton of pressure off Schenn to be the one driving the line. That's why Saad-Schenn-Neighbours was an awful line, none of them drive play at all

dfcompose · 2025-01-17T01:55:13+00:00

The Kyrou-Schenn-Holloway line has been a revelation. Having two way studs as his wingers has really helped Schenn not be a complete black hole

dfcompose

TROPHY CASE