Mark Embling

This would be cool, but would rely on #4 being implemented first to not be a bit annoying.

In my experience, re-targeting the project to >= .NET 4.7.2 solves the TLS issue as it'll use TLS 1.2 then automatically. That is the project which is using SagePayMvc, not...

I disagree. If I understood correctly, there was/is going to be an overall aim to the game which doesn't revolve around the concept of killing. If so, being shot every...

That would make more sense after a given time period, i.e. a few moments of holding fire. It also makes sense from a believability point of view as it's quite...

Are you sure this isn't a deliberate manipulation?

I saw this earlier (pain in the bum because you can't shoot what you can't see, no matter how souped-up your gun is), and I assumed it was deliberate. Haven't...

Maybe. I've never respawned in an illegal location though (don't you have checks for that?), and I assumed that was dealt with server-side, not that I've checked.

Ah right, well there you go then. In order to become invincible, you have to remove the behaviour you've provided for dealing with being killed. If you fudge that, I...

No, I mean invulnerable. I'm trying to say that invisibility nay be a side-effect of invulnerability hacks due to the need to muck around with the killing logic.

Opening up some sort of API so users can code their own bits with their own AI logic would be fantastic. Very complex, but great fun for us tinkerers.