call_sql("SELECT ..")
inside the wasm module. and then inside the host you can do with that information whatever you want.
The client simply returns an error that this is unsupported.
This is very simplified, bcs i abstracted these simple functions away using derive macros, in the end it feels more like you use a instance of a database object.
so you do object.query(my_statement)
and the rest happens hidden away from the user28601 t/s
29154 t/s
with the non O(n²) approach
Which surprises me, this is like 2x more than i had a month ago lol.
Time to git bisect xd
But defs worth to optimize it ig28601 t/s
29154 t/s
with the non O(n²) approach
Which surprises me, this is like 2x more than i had a month ago lol.
Time to git bisect xd
But defs worth to optimize it ig 28601 t/s
29154 t/s
with the non O(n²) approach
Which surprises me, this is like 2x more than i had a month ago lol.
Time to git bisect xd
But defs worth to optimize it ig 6442 t/s
6678 t/s
Which is still quite good if we assume the 1p vs 128p bencmark6442 t/s
6678 t/s
Which is still quite good if we assume the 1p vs 128p bencmark [client] got disconnect from server. reason: You have been banned (IP banned! Open a ticket on https://discord.kog.tw/)
{ config, pkgs, ... }: {
nixpkgs.overlays = [
(self: super: {
ddnet = super.ddnet.overrideAttrs (oldAttrs: {
version = "16.0";
src = pkgs.fetchFromGitHub {
owner = "DDNet";
repo = "ddnet";
rev = "16.0";
sha256 = "";
build once, get shasum, (or prefetch it), insert it, and runCGameContext::m_VoteCreator
to -1
when the player that started the vote leaves instead of keeping the invalid client ID around. Previously, this was causing the server to crash due an assertion in the IServer::GetAuthedState
function when a ban vote was aborted due to rcon authentication change being handled in the CGameContext::OnSetAuthed
function after the vote creator has already left the server. It was possible to cause this situation as the targe...