You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DIRTSAND declares the vault node Text_1/Text_2 columns as character varying(1024), but the client allows KI text notes to be (roughly) 2048 characters long.
This means that a player with a regular client can type a moderately long KI text note that DIRTSAND is unable to save. When that happens, the player has no indication that anything went wrong - the client accepts the text and caches it locally, but the server silently fails to save it to the vault. The player can only notice the problem after the client re-fetches the vault node from the server, i. e. after logging out and back in.
The only indication of the error is a log message on the server side:
.../dirtsand/AuthServ/AuthVault.cpp:1005:
Postgres UPDATE error: ERROR: value too long for type character varying(1024)
The same problem also applies to the neighborhood description text, which is also stored in Text_1 and AFAICT has no client-side limit at all.
The text was updated successfully, but these errors were encountered:
DIRTSAND declares the vault node
Text_1
/Text_2
columns ascharacter varying(1024)
, but the client allows KI text notes to be (roughly) 2048 characters long.This means that a player with a regular client can type a moderately long KI text note that DIRTSAND is unable to save. When that happens, the player has no indication that anything went wrong - the client accepts the text and caches it locally, but the server silently fails to save it to the vault. The player can only notice the problem after the client re-fetches the vault node from the server, i. e. after logging out and back in.
The only indication of the error is a log message on the server side:
The same problem also applies to the neighborhood description text, which is also stored in
Text_1
and AFAICT has no client-side limit at all.The text was updated successfully, but these errors were encountered: