Make scoring only possible with a higher amount of players on server #144
Conversation
|
A better solution would be to add a column But as said. I can test if the code compiles. I can't test if it works because I still havent figured out how to init the databases Need to tell me what solution should be implemnted and somebody else got to test it then, though. |
|
@teoman002 maybe you decide which solution because you tagged me :D or @bretonium knows if changing the database schema causes trouble |
|
solution 1 seems simple, so I suggest to do that. We can improve the code later™. |
teoman002
added
enhancement
By itself it doesn't, but we do not have the necessary infrastructure to automate schema migration, and asking administrators to do the migration manually, via .sql file, is a pain. We could add a check that the migration was applied and exit if it wasn't, but it is too much hassle for a simple issue. |
| @@ -4218,7 +4218,10 @@ class CSqlJob_Server_SendPlayerStatistics : public CSqlJob | |||
| void UpdateScore(CSqlServer* pSqlServer, int ScoreType, int Score, const char* pScoreName) | |||
| { | |||
| char aBuf[512]; | |||
|
|
|||
|
|
|||
| if (m_pServer->GetActivePlayerCount() > 8) | |||
|
|
||
|
|
||
| if (m_pServer->GetActivePlayerCount() > 8) | ||
| return |
There was a problem hiding this comment.
I wonder what this line without ; in the end does
Would solve #135