@Dev: Assigned to users with accepted pull requests on our main repository.

I think we shouldn't trigger rescue automatically. The player should rather press /r explicitly after they died, we could keep them in spectator mode until they do.

Auto-respawning is going to interact badly, e.g. if you respawn in speeders that push you into a death tile, that's a nice way to generate a lot of messages.

Security is your top priority: Pingora is a more memory safe alternative for services that are written in C/C++. While some might argue about memory safety among programming languages, from our practical experience, we find ourselves way less likely to make coding mistakes that lead to memory safety issues. Besides, as we spend less time struggling with these issues, we are more productive implementing new features. Your service is performance-sensitive: Pingora is fast and efficient. As explained in our previous blog post, we saved a lot of CPU and memory resources thanks to Pingora’s multi-threaded architecture. The saving in time and resources could be compelling for workloads that are sensitive to the cost and/or the speed of the system. Your service requires extensive customization: The APIs that the Pingora proxy framework provides are highly programmable. For users who wish to build a customized and advanced gateway or load balancer, Pingora provides powerful yet simple ways to implement it. We provide examples in the next section.