summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHello TMW <hello@themanaworld.org>2025-04-12 09:16:26 +0000
committerHello TMW <hello@themanaworld.org>2025-04-12 09:16:26 +0000
commitc41ba44fc31d7bb61dd572fe4cc36e7f52155242 (patch)
tree63400066c66b15fcae67f51f96f1143d35b8c615
parent25d8811e0e3f660869574e1f9e98a012b7430899 (diff)
downloadserverdata-c41ba44fc31d7bb61dd572fe4cc36e7f52155242.tar.gz
serverdata-c41ba44fc31d7bb61dd572fe4cc36e7f52155242.tar.bz2
serverdata-c41ba44fc31d7bb61dd572fe4cc36e7f52155242.tar.xz
serverdata-c41ba44fc31d7bb61dd572fe4cc36e7f52155242.zip
Server data submodule update: make client data up to date
Does what advertised - I've detected so far submodule commit pointer is stale and refers to old client data commit. Unfortunately it makes new items server knows unknown to client "by default".
m---------client-data0
1 files changed, 0 insertions, 0 deletions
diff --git a/client-data b/client-data
-Subproject 5b4960fa424bc5d180658d783ca561345deea72
+Subproject 96e63a9ffd3c62570314e76cf37fdea14f59930