Chat, GUID, Stats and Mapstats Logger[1.1.0.1][BF3]

[ImportBot]

Originally Posted by EBassie*:

 

Jep the the statsrecord is created later.

OK, so I've been doing work for nothing.

 

With a small db you dont get such errors :-)

Always the same:

Runs great on dev, sucks on Prod^^

Well, you don't DEV with 128.000 records

[ImportBot]

Originally Posted by EBassie*:

 

Here are some outputs from the plugin.

As you can see: sometimes it takes alot of seconds

 

Code:

[19:43:27] Info: OnLevelLoaded: MP_011 Gamemode: TeamDeathMatch0 Round: 0/1
[19:43:27] Info: update sql server
[19:43:27] Info: Started streaming to the DB-Server
[19:43:27] Info: OdbcConn was close, Reopen it, Current State is open
[19:43:33] Info: Status ID-Cache: 23 ID's in cache
[19:43:33] Info: Connection OdbcConn closed
[19:43:58] Info: Streamingprocess duration: 30,625 seconds

Code:

[19:29:46] Info: OnLevelLoaded: MP_001 Gamemode: TeamDeathMatch0 Round: 0/1
[19:29:46] Info: update sql server
[19:29:46] Info: Started streaming to the DB-Server
[19:29:46] Info: OdbcConn was close, Reopen it, Current State is open
[19:29:47] Info: Status ID-Cache: 22 ID's in cache
[19:29:47] Info: Connection OdbcConn closed
[19:30:04] Info: Streamingprocess duration: 17,8281 seconds

Code:

[19:17:32] Info: OnLevelLoaded: MP_018 Gamemode: TeamDeathMatch0 Round: 0/1
[19:17:32] Info: update sql server
[19:17:32] Info: Started streaming to the DB-Server
[19:17:32] Info: OdbcConn was close, Reopen it, Current State is open
[19:17:32] Info: Status ID-Cache: 23 ID's in cache
[19:17:32] Info: Connection OdbcConn closed
[19:17:48] Info: Streamingprocess duration: 16,7344 seconds
[19:19:41] Warning: Weapon: SoldierCollision is missing in the bf3.def file!!!

Code:

[19:42:40] Info: OnLevelLoaded: MP_018 Gamemode: RushLarge0 Round: 1/2
[19:42:40] Info: update sql server
[19:42:40] Info: Started streaming to the DB-Server
[19:42:40] Info: OdbcConn was close, Reopen it, Current State is open
[19:42:41] Info: Status ID-Cache: 33 ID's in cache
[19:42:41] Info: Connection OdbcConn closed
[19:43:32] Info: Streamingprocess duration: 52,4688 seconds

Code:

[19:30:02] Info: OnLevelLoaded: MP_018 Gamemode: RushLarge0 Round: 0/2
[19:30:02] Info: update sql server
[19:30:02] Info: Started streaming to the DB-Server
[19:30:02] Info: OdbcConn was close, Reopen it, Current State is open
[19:30:05] Info: Status ID-Cache: 31 ID's in cache
[19:30:05] Info: Connection OdbcConn closed
[19:31:15] Info: Streamingprocess duration: 72,9062 seconds

Code:

[19:54:15] Info: OnLevelLoaded: MP_007 Gamemode: ConquestLarge0 Round: 1/2
[19:54:15] Info: update sql server
[19:54:15] Info: Started streaming to the DB-Server
[19:54:15] Info: OdbcConn was close, Reopen it, Current State is open
[19:54:17] Info: Status ID-Cache: 58 ID's in cache
[19:54:17] Info: Connection OdbcConn closed
[19:55:49] Info: Streamingprocess duration: 93,5625 seconds

[ImportBot]

Originally Posted by CptChaos*:

 

@CptChaos

You shouldn't add manually columns to any tables.

If a weapon is missing you bf3.def files is faulty.

Is the bf3.def borked again? I recently updated it, a day before I updated to 1.0.0.3 of this plugin.

[ImportBot]

Originally Posted by Waterboyeee*:

 

I looked, but could someone explain this servergroup to me? I've got two servers that are going to merge to one and just wondering if I should mess with it or not.

[ImportBot]

Originally Posted by TheSweetiePie*:

 

Our 10.000 Ticket-Server Conquest Large with 32 slots produces 5.000 Chat-Entries during two days.

Is it possible to implement DB-pruning for logged serverchat dependent on a defined time-range (i. e. 30 days).

 

Me myself isn't able to code this, sorry.

Thx for answer!

 

Greets

[ImportBot]

Originally Posted by XpKiller*:

 

@Waterboyeee

Server groups could be used if you for example 4 Server ( 2 normal CQ and to 2 hardcore CQ)

Then you can assign Servergroup 0 for the normal Server and Servergroup 1 for the hardcoreserver.

 

The result would be that the plugin creates a merged ranking of the normal server and a merged ranking form the hardcore ones.

 

@TheSweetiePie

i will give you the needed query for that job.

But now i need to sleep now. :-)

[ImportBot]

Originally Posted by TheSweetiePie*:

 

Wow! Very smart of your!

I expect your solution really excitedly, because since tomorrow this server will be upgraded to 64 slots. Chat logging could get very excessive for our SQL-DB-Host.

 

Sleep well and nice dreams.

 

Kind regards!

[ImportBot]

Originally Posted by CptChaos*:

 

Keep in mind to run the query from console for the first time. Especially when you didn't purge the chatlogs it might take long to delete those records.

 

For future mantenance and to make it easier for you is to make it as a cronjob (Linux) or task (Windows) when the server isn't having high loads.

[ImportBot]

Originally Posted by XpKiller*:

 

@TheSweetiePie

 

Here is the Query:

Code:

DELETE
FROM tbl_chatlog
WHERE logDate < DATE_SUB(CURRENT_DATE(),INTERVAL '30' DAY);

This will delete all chat entries older than 30 Days.

 

Than you should run this statement:

Code:

OPTIMIZE TABLE tbl_chatlog;

[ImportBot]

Originally Posted by XpKiller*:

 

New Version 1.0.0.4

 

Changelog:

 

1.0.0.4

Increased stability --> ODBC errors shouldn't crash procon anymore.

Splited long transactions to avoid lock timeouts

fixed timeissue

implemented admin.yell, can be used in every message just add the yelltag in the beginning of the message

Usage: [yell,duration] --> [yell,3]Welcome on our server!

 

How to yell messages:

Every ingame messages can be yelled to the Player.

Just add the yelltag in front of every line of you message which should be yelled.

Usage:[yell,duration in seconds]Your messages

Like:[yell,3]Welcome on our server!

This would be yell for 3 seconds

Hint: You can mixed normal say and yell with out any problems.

 

Expect errors not tested well due my server is empty all the time :-(

 

 

Known Bugs:

Send stats to all player not working atm(bugged in plugin), will be fixed in next release.

[ImportBot]

Originally Posted by EBassie*:

 

Thanks XpKiller,

 

I already wanted to ask you for some nice neat little yell.

 

will start testing in a few minutes and will report back.

[ImportBot]

Originally Posted by Athlon*:

 

I'm testing it now.

 

Code:

[yell,10]%playerName% - Good to see you back with us!

Yells "[playername] - Good to see you back with us!" as expected for 10 seconds.

 

However,

 

Code:

[yell,10]%playerName% - Good to see you back with us!  Your Server rank here is %playerRank% of %allRanks%

Yells "[playername] - Good to see you back with us! Your Server rank here is %playerRank% of %allRanks%". The playerrank & allranks code shows instead of the actual numbers.

 

I tried this in the 'WelcomeStats' section.

[ImportBot]

Originally Posted by XpKiller*:

 

@Athlon

just

Code:

[yell,10]%playerName% - Good to see you back with us!

After that the plugin display the regular playerstats messages.

[ImportBot]

Originally Posted by Athlon*:

 

@Athlon

just

Code:

[yell,10]%playerName% - Good to see you back with us!

After that the plugin display the regular playerstats messages.

Right, but I would like to include their rank in the greeting (Yell) if possible.

[ImportBot]

Originally Posted by XpKiller*:

 

Good point not possible atm

 

i could added this to the next release.

[ImportBot]

Originally Posted by Athlon*:

 

Good point not possible atm

 

i could added this to the next release.

Thanks for getting back to me. I look forward to your next release!

[ImportBot]

Originally Posted by EBassie*:

 

These are my settings and they are all yelled like supposed to:

gyilv.png

 

Also the welcome stats work as a yell with these settings.

 

Great job XpKiller

[ImportBot]

Originally Posted by Mandizzy*:

 

XpKiller, I just came to ask you to add yell options and I see you're already several steps ahead - Thanks

 

BTW, I'm still running 1.0.0.3 and also recieved this error today only:

 

[17:27:06 08] Error: Error in Startstreaming:

[17:27:06 09] Index #0

[17:27:06 09] Message: [MySQL][ODBC 5.1 Driver][mysqld-5.5.17]Out of range value for column 'Playtime' at row 38

[17:27:06 10] Native: 1264

[17:27:06 10] Source: myodbc5.dll

[17:27:06 10] SQL: HY000

 

Was there ever a solution or cause found for this? My offset is not set - whatever default is.

[ImportBot]

Originally Posted by XpKiller*:

 

Pls try 1.0.0.4 is changed something regarding those time issue.

Also pls give feedback if you still get this error.

[ImportBot]

Originally Posted by TimSad*:

 

Does anyone have the full list of weapons yet? I still only have this in my "Keywords" plugin settings variable (I think I ended up adding the Magnum at the end)...

 

RPG-7{RPG}

Weapons/SCAR-H/SCAR-H{SCAR,SCAR-H}

USAS-12{USAS12}

M27IAR{M27}

AEK-971{AEK971,AEK}

Weapons/A91/A91{A91}

Weapons/AK74M/AK74{AK74,AK74M}

Weapons/G36C/G36C{G36C}

Weapons/G3A3/G3A3{G3A3,G3}

Weapons/Gadgets/C4/C4{C4}

Weapons/Gadgets/Claymore/Claymore{CLAYMORE,CLAY,LANDMINE}

Weapons/KH2002/KH2002{KH2002}

Weapons/Knife/Melee{KNIFE}

Weapons/M416/M416{M416}

Weapons/MagpulPDR/MagpulPDR{MagpulPDR}

Weapons/MP412Rex/MP412REX{MP412REX,REX,MP412}

Weapons/MP443/MP443{MP443}

Weapons/P90/P90{P90}

Weapons/Sa18IGLA/Sa18IGLA{Sa18IGLA,Sa18,IGLA}

Weapons/UMP45/UMP45{UMP,UMP-45,UMP45}

Weapons/XP1_L85A2/L85A2{L85A,L85}

Taurus .44{MAGNUM, 44 MAGNUM, 44}

[ImportBot]

Originally Posted by XpKiller*:

 

The plugin reads the weapons from the bf3.def file. Those keyword are just human friendly names for some weapons for the ingame commands.

[ImportBot]

Originally Posted by TimSad*:

 

The plugin reads the weapons from the bf3.def file. Those keyword are just human friendly names for some weapons for the ingame commands.

Well, all my players constantly try finding their ranking for their favorite weapons with no success. Most every time they just get that pesky message "Specific Weapon not found!" Are all the BF3 weapons even found in the bf3.def file?

[ImportBot]

Originally Posted by bananaSkill*:

 

@EBastard

 

you need to increase the innodb_lock_wait_timeout to a high value

The transaction get a timeout from the server.

Default is 50 i put it on 150, did not know what you meant with 'high' is that ok or does it need to be allot higher ?

[ImportBot]

Originally Posted by XpKiller*:

 

@Timsad could you post examples ?

Not all weapons are reported by the gameserver.

Also you can set alternative names for every weapon in the keyword list.

 

@bananaskill

Normally the default value is ok. This value only needs to be changed if you have problems.

[ImportBot]

Originally Posted by bananaSkill*:

 

@XpKiller, EBastard asked me to change the value to 'high'

[ImportBot]

Originally Posted by Narf!*:

 

Yell working fine for me. But do you think it would be possible to add pyell? That would be rly awesome. Asking for that because of sometimes there are some guys asking for their rank at the same time. I think pyell would be nice in this situations.

[ImportBot]

Originally Posted by krov7*:

 

I can't get any yell commands working.

EBastard, how the heck did you get that stuff to work?

 

Tried these, no variant or tweaking seems to work:

[yell,3]%playerName% is rank %playerRank% of %allRanks%. Best killstreak: %killstreak%

[yell,3] Hey %playerName%!

[ImportBot]

Originally Posted by XpKiller*:

 

@Narf!

i couldnt test much but try to set "send stats to all Player" to No (pyell is already implemented but not useable in this way yet but properly in the next release)

But i also planned to do this (pyell)

 

Its on the list for next release.

 

@krov7

Just put the yelltag in the beginning of your message like: [yell,3]Welcome to our server!

[ImportBot]

Originally Posted by krov7*:

 

I copy pasted "[yell,3]Welcome to our server! ", doesn't seem to work for some reason. I have updated the plugin, too

[ImportBot]

Originally Posted by EBassie*:

 

Hey XpKiller,

 

think I found a bug in the YELLing..

As you may know the player sets the scope of his message with:

 

@ = Private scope (only player sees the incoming response)

! = Public scope (all players see the incoming response)

 

So when a player uses @rank, only the player sees the YELL.

But when a player uses !rank it should be shown to all players.

 

It seems there is a mix-up with the "Send stats to all Players" Setting.

 

The public scope should probably only work when "Send stats to all Players = Yes"

 

But when using !rank with "Send stats to all Players = Yes" Procon returns this error message:

Code:

admin.yell 6 Your Score: 1611863  4182 Kills 1139 HS  2630 Deaths K/D: 1,59 all
InvalidArguments
admin.yell 4 Your Serverrank is: 2 of 69483 all
InvalidArguments

I think the code should be (yell time on end of the line):

Code:

admin.yell "Your Score: 1611863  4182 Kills 1139 HS  2630 Deaths K/D: 1,59" 4 all
OK

Without the quotes it is not working.

 

 

 

When "Send stats to all Players = No" !rank will be YELLed to only the player and works like below.

When using @rank it works as intended and is shown only to the player:

Code:

admin.yell Your Score: 1611863  4182 Kills 1139 HS  2630 Deaths K/D: 1,59 6 player EBassie
admin.yell Your Serverrank is: 2 of 69483 4 player EBassie
OK

I hope I did not make a mess of this post. It was hard enough to figure it out and write it down