Lobby/Stage Chat Logger - 1.5 Source.

[qet123]

Nothing special, took me 5 min .

Lobby Logger:

MMatchServer_Channel.cpp, look for:

	
	
bool MMatchServer::ChannelChat(const MUID& uidPlayer, const MUID& uidChannel, char* pszChat)
Paste under:

	
	
pCmd->AddParameter(new MCommandParameterInt(nGrade));
This:

	
	
	if( uidChannel == pObj->GetChannelUID() )
	{
		LOG(LOG_PROG, "[Lobby] | %s : %s ", pObj->GetName(), pszChat);
	}

Stage Logger:

MMatchServer_Stage.cpp, look for:

	
	
bool MMatchServer::StageChat(const MUID& uidPlayer, const MUID& uidStage, char* pszChat)
Paste under:

	
	
pCmd->AddParameter(new MCommandParameterString(pszChat));
This:

	
	
	if( uidStage == pObj->GetStageUID() )
	{
		LOG(LOG_PROG, "[Stage] | %s : %s ", pObj->GetName(), pszChat);
	}

Note:

LOG_PROG would display in both log file and matchserver screen.
LOG_FILE would display only in log file of the matchserver.

Photo from matchserver screen:

Spoiler:

Code from matchserver log file:

../Log
[07/04/12 00:04:43] [Lobby] | RaGEZONE : This is lobby. 
[07/04/12 00:04:49] [Stage] | RaGEZONE : This is stage.

Adding custom file: (Didn't test);

To add Log File.

MCommandCommunicator.h :

Search for:

enum _LogLevel	{

add:

LOG_FILELOBBY = 8,

MCommandCommunicator.cpp

search for:

void MCommandCommunicator::LOG(unsigned int nLogLevel, const char *pFormat,...)

{

add:

if (nLogLevel == LOG_FILELOBBY){
  FILE * pFile;
  pFile = fopen ("Logs/lobby.txt","w");
  if (pFile!=NULL)
  {
		va_list args;
		static char temp[1024];


		va_start(args, pFormat);
		vsprintf(temp, pFormat, args);
    fputs (temp,pFile);
    fclose (pFile);
  }



}else

To use function:

LOG(LOG_FILELOBBY, "[Lobby] | %s : %s ", pObj->GetName(), pszChat);

Like if you gonna use it

[MentaL]

[Mr_Troy]

Wouldn't it be better to create separate files from the MatchServer log. This is very unorganized and is hard to read through.

[CobraBite]

Don't you think the matchserver will be exploded if you will have lot's of players : < ? I rather use the Log folder only.

[qet123]

Wouldn't it be better to create separate files from the MatchServer log. This is very unorganized and is hard to read through.

It's very simple one, the new file would make it perfect

Don't you think the matchserver will be exploded if you will have lot's of players : < ? I rather use the Log folder only.

LOG_FILE would display only in log file of the matchserver.

[CobraBite]

Wouldn't it be better to create separate files from the MatchServer log. This is very unorganized and is hard to read through.

Just make another function like the LOG_FILE and rename it to something else.

[Ronny786]

You suggested me some new ideas ^_^ Thanks. <3

[Joe9099]

It may be a mess, but it's actually something useful from u for once.

[qet123]

It may be a mess, but it's actually something useful from u for once.

Y U NO LOVE ME

You suggested me some new ideas ^_^ Thanks. <3

Well, it's easy and usefull, anyway your welcome

[Mocro]

To add Log File.

MCommandCommunicator.h :

Search for:

enum _LogLevel	{

add:

LOG_FILELOBBY = 8,

MCommandCommunicator.cpp

search for:

void MCommandCommunicator::LOG(unsigned int nLogLevel, const char *pFormat,...)

{

add:

if (nLogLevel == LOG_FILELOBBY){
  FILE * pFile;
  pFile = fopen ("Logs/lobby.txt","w");
  if (pFile!=NULL)
  {
		va_list args;
		static char temp[1024];


		va_start(args, pFormat);
		vsprintf(temp, pFormat, args);
    fputs (temp,pFile);
    fclose (pFile);
  }



}else

To use function:

LOG(LOG_FILELOBBY, "[Lobby] | %s : %s ", pObj->GetName(), pszChat);

[qet123]

To add Log File.

MCommandCommunicator.h :

Search for:

enum _LogLevel	{

add:

LOG_FILELOBBY = 8,

MCommandCommunicator.cpp

search for:

void MCommandCommunicator::LOG(unsigned int nLogLevel, const char *pFormat,...)

{

add:

if (nLogLevel == LOG_FILELOBBY){
  FILE * pFile;
  pFile = fopen ("Logs/lobby.txt","w");
  if (pFile!=NULL)
  {
		va_list args;
		static char temp[1024];


		va_start(args, pFormat);
		vsprintf(temp, pFormat, args);
    fputs (temp,pFile);
    fclose (pFile);
  }



}else

To use function:

LOG(LOG_FILELOBBY, "[Lobby] | %s : %s ", pObj->GetName(), pszChat);

Thanks for developing it, added to the main post.

[Vusion]

#include <fstream>

	ofstream chatLog;
	chatLog.open("ChatLogs.txt", ios::app);
	sprintf(szLog, "%s From: %s To: %s: %s\n", Time(), pObj->GetName(), pszTargetName, pszMessage);
	chatLog << szLog;

char* Time( )
{
	time_t lTime;
	struct tm* TM;

	lTime = time( NULL );
	TM = localtime( &lTime );

	char szBuffer[25];
	sprintf( szBuffer, "[%d:%d:%d]", TM->tm_mday, TM->tm_hour, TM->tm_min );

	return szBuffer;
}

[WizCoder]

Sigh I wish people ^ would just specify what they had changed instead of just making changes and leaving it up to the viewer to go to the top and look and the default then compare it to the latest just to see what's new.

[Vusion]

Sigh I wish people ^ would just specify what they had changed instead of just making changes and leaving it up to the viewer to go to the top and look and the default then compare it to the latest just to see what's new.

Those aren't edits done to qet's source if that's what you're referring to.

Anyway, I never said I was spoonfeeding, so yeah, have fun.

[ThePhailure772]

"%s%s"

You just made the chatroom crash even easier.

[Solaire]

"%s%s"

You just made the chatroom crash even easier.

What Jacob is trying to say here is to use try and except handlers or make sure the chat doesn't contain % since that might result into buffer overflow (and crash your server).

try-except Statement (C++)

Putting the vsprintf in the try block would do the trick, clean your args in the except block and then return.

[Military]

Sigh I wish people ^ would just specify what they had changed instead of just making changes and leaving it up to the viewer to go to the top and look and the default then compare it to the latest just to see what's new.

It's call making them learn ..