Many maps on server = problem

[rotacak]

We want to upload all existing maps to our server. We uploaded about 1,6GB maps and when someone want to connect then error message appear "Unpure client detected, invalid pk3 files referenced". Tremulous server can't handle so many maps or what?

[kevlarman]

We want to upload all existing maps to our server. We uploaded about 1,6GB maps and when someone want to connect then error message appear "Unpure client detected, invalid pk3 files referenced". Tremulous server can't handle so many maps or what?

there's a hard limit that causes weird things to happen, but your error is from people connecting when they don't have the map and don't have downloads enabled

[Thorn]

We discovered on Fun-Zone a few months ago that there is a limit of 128 PK3's. Any additional maps are not catalogged.

[rotacak]

kevlarman: that error appear with any map (atcs) even if you has that map. Maybe it is one from "weird things".

Thorn: we currently have about 170 maps and it is ok yet, only !listmaps commands know 128 of them.

[David]

Have you changed any of them?  Screwed around with data-1.1.0 or vms-1.1.0 or whatever?

[Undeference]

your error is from people connecting when they don't have the map and don't have downloads enabled

More likely, that is caused by a too long info string, indicated by "BIG Info string length exceeded". Reducing the number of maps or disabling purity checking (don't do that) will solve that.

[rotacak]

Have you changed any of them?  Screwed around with data-1.1.0 or vms-1.1.0 or whatever?

Nothing was changed, only was downloaded all maps from tremcentral and uploaded to server = ok. Then downloaded all maps from MG repository and uploaded among existing maps on server and this happen. We deleted all maps with suspicious names, but that not helped. Server was again ok after was deleted few maps.

[Amanieu]

your error is from people connecting when they don't have the map and don't have downloads enabled

More likely, that is caused by a too long info string, indicated by "BIG Info string length exceeded". Reducing the number of maps or disabling purity checking (don't do that) will solve that.

The systeminfo string can't hold all the maps in it, therefore it omits some pk3s from the pure list, therefore the client can't load them. Easy fix: Remove CVAR_SYSTEMINFO from sv_pakNames.