Well. Sometimes there are different bugs. Like my settings reset randomly on grangerhub for some reason. and is fkin with my autogens o.O
lol yea its done that a few times to me. might start backing up certain files to be safe
this is happening to me right now 
Haven’t had the autogen bug yet, but it isn’t really a problem for me anyway. You should probably do what I did, all of my important settings are saved in a few cfgs (tremfusion team binds cvars yay) and if the autogen ever fucks up I’ll just have to /exec setup.
Also I know of this forum existence because I tried to log on GrangerPub server in Trem, and couldn’t enter in the game because of a maxconfigstrings error or something like that. As I searched on google for help, I saw a link to this website. Halp please?
Ooh! I’ve had same problem!
I know, that’s why I moved your post here ;).
Yea I know 
Also Hi Spark! 
what hud are you using?
I believe this is both server and client side issue. I believe this message is in regards to the serverinfo string which is sent to the client on initial connect.
The problem is, that the string is “too-big”- this string is going to contain various Cvar’s as well as information regarding each player connected (including they’re names with color codes).
[[ I’m probably getting some of this info wrong, as some is sent initially and there is also updates periodically for the client to choose the correct “model”, whether all this is sent on connect (prior too “has entered the game” is yet to be determined. ]]
As-is, ioquake3 and tremulous both use fixed size buffers for this cruft; and most of it is just that, cruft. Clients don’t need all the cvars listed in “serverinfo” (which has become bloated in tremulous); and of the information that is sent, not all of it was ever fully implemented.
- Servers should send less info.
- Clients should be capable of processing at-least 1400bytes at a time. May also need to handle fragments, though shouldn’t be problem.
To give you an idea of what I’m talking about, connect to grangerhub. Execute “/configstrings”. You can see, for example that cvars for suddenDeath time, and the QVM version info (slacker …[yadayada] lakitu…); which are never used inside the client, except to be listed in the “serverinfo” menu from the browser menu.
edit:
Also, my client MAXCONFIGSTRING is 1024 bytes. I believe this is typical for most if not all tremulous clients. I have not checked GPP.
I have the same problem
This is happening to me now. Usually it will happen once and ill try to reconnect and i can enter. But now im unable to join because its giving me this error almost everytime. Sometimes there are different errors
Did you take note of which maps were on the server at the time, and how many players were online?
That makes sense given what we know about this bug. This bug is related to the network code and we are close to fixing it for 1.3 at least. We have determined what triggers this bug, there are 3 factors that contribute to it, a large number of players on the server, a large number of buildables on the server, and a large number of pk3 files on the server. This bug only affects players who are not already on the server.
Treecannon has a relatively high number of build points that overrides the default bp settings, so when there are a lot of players on treecannon, and a lot of buildables built, the bug could be triggered.
1 Like
I have never received this error. I am running tremfusion.
i havent received it lately but when i do it persists for weeks. sometimes i dont even get the error. it just sends me back to trems main menu without an error message
perhaps bad timing?
perhaps good timing?
This bug has been known to occur on all clients.
This just happened to me.