Notpron Forums

why not edit your post? keeps stuff tidy and makes the page smaller

Editing doesn't bump or flag the thread as having new content. I wouldn't want to risk taxing people's short attention span with having to spot my edits on their own.. It's just easier and safer to add a new post.

How about modifying things to report the game events to the built-in Epic stats engine instead of the clientside logging ?

What events are currently handled? It appears that only goals and kills are.

It would make more sense to pass all relevant events: Good/bad passes, shots on goal/goals, saves, tackles, badkills, etc..

How difficult would this be implement?

Not difficult at all... now get to work..

Ok. Let's start with the simple question: What stats do we want to track in Deathball?

Here's what TV has defined in the clientside csv output already:

1. Team colour / Player's Name
2. Team Score / Player's ID Hash
3. Team Possession % /Player's Team (0=red,1=blue)
4. Assists
5. Bad Kills
6. Bad Passes
7. Ball Hold Time
8. Ball Touches
9. Failed Saves
10. Goals
11. Good Passes
12. Hat Tricks
13. Home Runs
14. Interceptions
15. Kills
16. Missed Goals
17. Saves
18. Self Goals
19. Tackled
20. Tackles
21. Volleys
    [/list=1]
    
    Sample loglines are found earlier in this thread.
    
    Are these enough or too much to define as all we need in Deathball Stats?

Saves/Failed saves
Kills/killed
Tackels/takeled
Interceptions
"Redirects" = volley an enemy ball
Defects/defected
Ball touches
Ball hold time
Good passes/bad passes
-good passes %
Goals/self goals
-TD's
-Volley Goals
-Powered goals
-Pass goals
-Hat tricks
-Goal post hits "Clanks"
-missed chances = post hit, keeper saves, ball carrier gets killed in enemy pbox
Assists
Time in enemy half %/time in own half %
Team score/team possession %
Enemy score/enemy possession %

boosts!

Wow, thanks for putting work into this imag

Any news to share agout stats line insertions?

David? Robert?

awesome feedback -

I would liek to make a suggestion for stats at the end of matches/pubs etc..

do like hockey does. 3 stars of the game, can come from either of the teams. decided upon effectiveness

just some overlaying text or whatever on the screen announcing the top 3 stars of the game. would be cool.

I'm trying to figure out a way to run a check of GUIDs to players for league games (you don't want anyone cheating).

Is there a command to write to the console screen the name and GUID of each player (then log that output)?

I realize this is the long way around and having a class that wrote each GUID along with the players alias and his stats to the server log would be a better way to do it.

As of right now, my only thinking is to have the referee or match admin check each players GUID to make sure it matches their recorded alias before the match starts.

Would their be a way to make a mutator that did this? Extended the playerstats class?

There are a few different ways this can be checked.

1) The running native ut2004 stats output. Lists player nick/ip/guid and stats id as they connect.

2) UTAN: monitors the server and tracks each person's nick/guid/ip into a web-based database

3) ServerEXT : provides playerjoinsdump as well as extending the gamespy query protocol to respond to player guid queries.

4) AntiTCC: also provides a way to see all the player guid

5) Via webadmin. You see the list there.

utan pwns (but it wouldnt really provide any use for DB, apart to ban ash from all the DB servers ever)

Coming soon to UTAN, selectable length suspensions.

If the Deathball team were to put proper stat logging in their code, and report that stuff to the built in stat logger, I would be happy to pur in specific Deathball support in to OLStats, which already does output full HTML stats.

Just a thought.