source-sdk-2013 VS Polly

It's literally on Github. https://github.com/ValveSoftware/source-sdk-2013

here's the full thing https://github.com/ValveSoftware/source-sdk-2013/blob/0d8dceea4310fde5706b3ce1c70609d72a38efdf/mp/src/game/shared/shot_manipulator.h

please don't try to continue arguing this because, while i can't say i'm an authority of this subject, i've studied far more than enough about it to say that you're not making sense and if you really don't trust me then you can simply do what i did: read articles, read the source code, learn from other people who are more knowledgeable

I have just finished Solar's complex Demoknight Guide. And I know the code behind rampsliding and basic SourceEngine&TF2 movement code.

Hi! The only other stats you can change without editing the code is weapon damage by editing skill.cfg inside the cfg folder. Weapon recoil and fire rate can only be changed by editing the code. The source code for Half-Life 2 can be found here: https://github.com/ValveSoftware/source-sdk-2013

Weapon_rpg.cpp is in src/game/shared/hl2mp as an example

Also, while this uses leaked code, Valve has officially released the Source SDK 2013, which does include all the hl2 specific code, so if you copy over the assets from hl2, it can run just like normal.

the random spread is biased towards the centre, pretty easy to observe and heres the code for it https://github.com/ValveSoftware/source-sdk-2013/blob/master/mp/src/game/shared/shot_manipulator.h

In our applications, we should wrap all requests to remote services in code that implements a retry policy that follows one of the strategies I listed earlier. If you are a .NET developer like myself, you may be familiar with the Polly library. Golang has a library called Retry, and there are numerous third-party libraries for Python and Java.

Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?

D'Oh! Sorry, not PolySharp. I meant Polly. Too many similarly-named libraries!

Everywhere I've worked with AGs, we've worked with the application team to add retry logic to help make things a bit more seamless to end users. There are libraries out there that can make this pretty easy - Polly is one that I've used a few times, but there are others.

Fallacy 1: The network is reliable. If system 2 works perfectly well, but is not accessible for service 1 due to network issues, service 2 is still unavailable. This is why timeouts, service breakers and retry policies exist. A great tool for .NET to handle common network issues is Polly, but even when using a tool like this, the network is still not completely reliable.

I see. Then I don't have any better idea right now, but I do want to suggest that if your script is mostly API calls and you want to be able to deal with failures then take a look at the polly library: https://github.com/App-vNext/Polly

Runs in containers nicely, has good integration with Kafka, RabbitMQ, gRPC, etc. for Microservices communication. Implements resiliency patterns you'd want in Microservices via Polly. Has a decent Dependency Injection framework built in by default.

It's in no way hidden. But I use Polly all the time.

Depending if the sender or the reciever is down, you can also try Polly http://www.thepollyproject.org/