I have a problem with this method:

void CASGame::ClientPrintAll( int iMsgDest, const CASString& szMsgName, 
					const CASString& szParam1, const CASString& szParam2, const CASString& szParam3, const CASString& szParam4 )

CASString is a string class, which only stores a pointer to a char*.

This function is exposed as:

"void ClientPrintAll(HUD iMsgDest, const string& in szMessage, const string& in szLine2 = \"\", "
		"const string& in szLine3 = \"\", const string& in szLine4 = \"\", const string& in szLine5 = \"\")"

Where HUD is an enum.

The function is called like this:

g_Game.ClientPrintAll( HUD_PRINTNOTIFY, "Changing map" );

Where g_Game is an instance of CGame, and HUD_PRINTNOTIFY is one of the HUD values.

For some reason, the last 2 strings are empty. Not empty as in pointing to a string ""; the pointer itself is NULL. The string class is written in such a way that this can never happen, which means that something else must be wrong.

The calling convention is correct, and i can't see what else could possibly be wrong.

After further testing i have determined that the strings are only null if the method is called like this:

void test()
{
    g_Game.ClientPrintAll( HUD_PRINTNOTIFY, "abc" + "test" );
}

In this case, the last parameter is null, but if another addition occurs, the second to last parameter is also null.

It seems that for every addition that occurs, one more default parameter is not initialized.

This is the registration of the entire string class: http://pastebin.com/iStrQEhi

RegisterSCScriptForwardDeclareString is called first to register the type, after that RegisterSCScriptASString is called to register the remainder.

CASDocumentation forwards all registration calls and handles the result, so nothing special goes on there.

REGISTER_VARARGS_FUNCTION is a macro that registers overloads for a function that accepts ?& in types.

I'll see if i can get the latest version up and running in our codebase.

I've upgraded to 2.30.0 WIP; the problem still occurs. Since you have been unable to reproduce the issue, i suspect the problem is somewhere in my string class, but so far i haven't seen any problems.

I'll set up the string class in a self contained program and see if the problem occurs there.