career statistics/records
career statistics/records
Howdy again,
I really enjoy my bygfoot and hope that 1.9 will be even better. You know what I sometimes would like, especially when I am selling off old players? Something perhaps in the history section that tells me who has played the most matches for my team at each of the four positions and something that tells me who has scored the most goals (during my entire career, not just the year). Maybe the top three in each category. From what I can tell, this would require adding a new section of your database that would store the cumulative statistics for each player during their time with my team.
A different but related thing would be much simpler to implement, because Bygfoot already stores the data for it: again in the history section, something that lists which teams have won the most top division championships and which players have won the awards given each year the most times (from all teams, not just my own). Also, what my average ranking within the league has been (including lower divisions if applicable). Obviously, I can gather all of this data myself, but it doesn't seem it would be that hard to put it in the history section or in a new career stats section. It would help give me goals like improvement of my career average, or demolition of records, etc.
Also, including the teams that have averaged the highest ranking might also be nifty. That way, I could see that my team has averaged let's say 7th place and that some other team has averaged 3rd. I could try to play until I have been the best, despite having started in 5th division.
Just ideas that I didn't see on the list.
Cheers
I really enjoy my bygfoot and hope that 1.9 will be even better. You know what I sometimes would like, especially when I am selling off old players? Something perhaps in the history section that tells me who has played the most matches for my team at each of the four positions and something that tells me who has scored the most goals (during my entire career, not just the year). Maybe the top three in each category. From what I can tell, this would require adding a new section of your database that would store the cumulative statistics for each player during their time with my team.
A different but related thing would be much simpler to implement, because Bygfoot already stores the data for it: again in the history section, something that lists which teams have won the most top division championships and which players have won the awards given each year the most times (from all teams, not just my own). Also, what my average ranking within the league has been (including lower divisions if applicable). Obviously, I can gather all of this data myself, but it doesn't seem it would be that hard to put it in the history section or in a new career stats section. It would help give me goals like improvement of my career average, or demolition of records, etc.
Also, including the teams that have averaged the highest ranking might also be nifty. That way, I could see that my team has averaged let's say 7th place and that some other team has averaged 3rd. I could try to play until I have been the best, despite having started in 5th division.
Just ideas that I didn't see on the list.
Cheers
Re: career statistics/records
i'm pretty sure it will you can try out the cvs version if you like (you can get one with the bygfoot-update script).kingduct wrote:I really enjoy my bygfoot and hope that 1.9 will be even better.
i don't think i like this. the player stats are mostly removed from 1.9 (or, more precisely, since 1.9 is written from scratch, never got added) because to have clear, simple and general code, all players should have stats; but there are thousands of players in the game, and the player stats got simply too big to handle. too big for my taste, anyway.You know what I sometimes would like, especially when I am selling off old players? Something perhaps in the history section that tells me who has played the most matches for my team at each of the four positions and something that tells me who has scored the most goals (during my entire career, not just the year). Maybe the top three in each category. From what I can tell, this would require adding a new section of your database that would store the cumulative statistics for each player during their time with my team.
now these are ideas that sound interesting. i won't add them to 1.9.0, but they might get implemented later. or some of them. in germany, there's a so-called 'ewige tabelle' -- 'forever table', in which all teams that have been part of the first league are listed with points and goals etc. from all of their first league matches. naturally, bayern munich is first. i could imagine doing something like this.A different but related thing would be much simpler to implement, because Bygfoot already stores the data for it: again in the history section, something that lists which teams have won the most top division championships and which players have won the awards given each year the most times (from all teams, not just my own). Also, what my average ranking within the league has been (including lower divisions if applicable). Obviously, I can gather all of this data myself, but it doesn't seem it would be that hard to put it in the history section or in a new career stats section. It would help give me goals like improvement of my career average, or demolition of records, etc.
Also, including the teams that have averaged the highest ranking might also be nifty. That way, I could see that my team has averaged let's say 7th place and that some other team has averaged 3rd. I could try to play until I have been the best, despite having started in 5th division.
gyözö
p.s.: your english sounds fairly sophisticated, wouldn't you like to help us with the live game commentary in 1.9? have a look at this post.
Press any key to continue or any other key to quit.
player stats
Again, I find your logic pretty convincing...
What about the possibility of only keeping statistics for the user's team? Just as Real Madrid fans are attached to Raul even though he is approaching mediocrity, I become attached to my players and would like to at least remember them somehow. I know that only keeping stats for the user's team would be a bit strange and unsymmetrical, but we only care about our own players anyway. A single stat would keep me content: number of games played. That is the clearest indication of what I felt about the player. Even number of seasons for my team would give me the basic idea, though ties would be more frequent.
Then again, there are other aspects that are more important...and in general I think that I agree with the simplicity that you believe in, after all M.U.L.E. is my favorite computer game and it was super simple. So, my adjusted vote is for games or seasons played only for my team, but if that won't be in your plans, that seems like a fine decision.
I'm taking a look at the commentary. The problem is that I actually don't know a whole lot about football because I'm American. Furthermore, what I do know is mostly in Spanish because I lived in Spain and currently live in Ecuador. So, I might get terminology wrong (for instance, I was once corrected because I always say "autogoal" and it turns out that in English it is "Own goal"). What I may be able to do is some editing of the grammar, etc, though I understand that you all are probably intentionally using shortened grammar to avoid over-wordiness.
(on a side-note, I agree with the option of verbose and non-verbose commentary...an option to eliminate all pass commentary). Maybe the non-verbose could condense the passing to indicate when a team has had five consecutive good passes, or ten, etc (like how Unreal Tournament announces after five straight kills that you are on a killing spree, Bygfoot could announce that you are on the attack, or dominating ball control after 10 straight passes, etc.
Will check out 1.9 too, hope it doesn't wipe out my 1.8 settings.
Take it easy
What about the possibility of only keeping statistics for the user's team? Just as Real Madrid fans are attached to Raul even though he is approaching mediocrity, I become attached to my players and would like to at least remember them somehow. I know that only keeping stats for the user's team would be a bit strange and unsymmetrical, but we only care about our own players anyway. A single stat would keep me content: number of games played. That is the clearest indication of what I felt about the player. Even number of seasons for my team would give me the basic idea, though ties would be more frequent.
Then again, there are other aspects that are more important...and in general I think that I agree with the simplicity that you believe in, after all M.U.L.E. is my favorite computer game and it was super simple. So, my adjusted vote is for games or seasons played only for my team, but if that won't be in your plans, that seems like a fine decision.
I'm taking a look at the commentary. The problem is that I actually don't know a whole lot about football because I'm American. Furthermore, what I do know is mostly in Spanish because I lived in Spain and currently live in Ecuador. So, I might get terminology wrong (for instance, I was once corrected because I always say "autogoal" and it turns out that in English it is "Own goal"). What I may be able to do is some editing of the grammar, etc, though I understand that you all are probably intentionally using shortened grammar to avoid over-wordiness.
(on a side-note, I agree with the option of verbose and non-verbose commentary...an option to eliminate all pass commentary). Maybe the non-verbose could condense the passing to indicate when a team has had five consecutive good passes, or ten, etc (like how Unreal Tournament announces after five straight kills that you are on a killing spree, Bygfoot could announce that you are on the attack, or dominating ball control after 10 straight passes, etc.
Will check out 1.9 too, hope it doesn't wipe out my 1.8 settings.
Take it easy
Re: player stats
this would be much simpler; i could add an additional player struct variable keeping count about career matches (which could be deleted each time a player is transferred).kingduct wrote:What about the possibility of only keeping statistics for the user's team? Just as Real Madrid fans are attached to Raul even though he is approaching mediocrity, I become attached to my players and would like to at least remember them somehow. I know that only keeping stats for the user's team would be a bit strange and unsymmetrical, but we only care about our own players anyway. A single stat would keep me content: number of games played. That is the clearest indication of what I felt about the player. Even number of seasons for my team would give me the basic idea, though ties would be more frequent.
mule? what's that?after all M.U.L.E. is my favorite computer game and it was super simple.
that would make you a candidate for the spanish translation sadly, i didn't receive a spanish translation yet (for 1.8; for 1.9 there wasn't a string freeze yet); sadly, because there are millions and millions of spanish speaking football enthusiasts.I'm taking a look at the commentary. The problem is that I actually don't know a whole lot about football because I'm American. Furthermore, what I do know is mostly in Spanish because I lived in Spain and currently live in Ecuador.
oh, anything you like. anything that makes it betterSo, I might get terminology wrong (for instance, I was once corrected because I always say "autogoal" and it turns out that in English it is "Own goal"). What I may be able to do is some editing of the grammar, etc, though I understand that you all are probably intentionally using shortened grammar to avoid over-wordiness.
yes, i'm planning to add an option for this.(on a side-note, I agree with the option of verbose and non-verbose commentary...an option to eliminate all pass commentary).
one can see who's attacking anyway (the tendendy bar).Maybe the non-verbose could condense the passing to indicate when a team has had five consecutive good passes, or ten, etc (like how Unreal Tournament announces after five straight kills that you are on a killing spree, Bygfoot could announce that you are on the attack, or dominating ball control after 10 straight passes, etc.
shouldn't do so. 1.9 creates a folder HOME/.bygfoot-1.9 and shouldn't interfere with 1.8. of course you can forget savegame compatibility.Will check out 1.9 too, hope it doesn't wipe out my 1.8 settings.
gyözö
Press any key to continue or any other key to quit.
hey i just had a thought. yeah another hair brained scheme
Im not sure how gyozo handles the "history" data. I recognise the last thing we want are
A complicating the bygfoot code
B making the save games files even bigger, thus slowing down load up and save times.
Its not always a good thing to split but this might be an exception. What if the history side of things is saved as a diferent file? and I mean the complex indepth stuff kingduct was talking about. Like across multiple seasons. etc. with this info removed from the autosave files(say at the end of each season) it will be quicker. Save it in some sort of common data base format so that users can either import into there own db application or make a seperate bygfoot historydb application.
I had a quick look at a bygfoot saved zip but couldnt see or understand wher ethe history and player info could be.
the reason why I say make it a db format is because everytime someone decides "wouldnt it be nice if ..." i could query how many boots my inside right forward went thru last season. we either go forget it or gyozo has to code in a whole heap of stuff. If it were a db format tho anyone could russel up their db app load in bygfoot_history_stats file and write their own query. I am unfamiliar with linux database apps. I do know that this would work fairly well in winxps access. If someone writes a new query they can make it available here somewhere.
The bygfoot history stats analyser builds itself
Im not sure how gyozo handles the "history" data. I recognise the last thing we want are
A complicating the bygfoot code
B making the save games files even bigger, thus slowing down load up and save times.
Its not always a good thing to split but this might be an exception. What if the history side of things is saved as a diferent file? and I mean the complex indepth stuff kingduct was talking about. Like across multiple seasons. etc. with this info removed from the autosave files(say at the end of each season) it will be quicker. Save it in some sort of common data base format so that users can either import into there own db application or make a seperate bygfoot historydb application.
I had a quick look at a bygfoot saved zip but couldnt see or understand wher ethe history and player info could be.
the reason why I say make it a db format is because everytime someone decides "wouldnt it be nice if ..." i could query how many boots my inside right forward went thru last season. we either go forget it or gyozo has to code in a whole heap of stuff. If it were a db format tho anyone could russel up their db app load in bygfoot_history_stats file and write their own query. I am unfamiliar with linux database apps. I do know that this would work fairly well in winxps access. If someone writes a new query they can make it available here somewhere.
The bygfoot history stats analyser builds itself
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?
i've implemented some career stats for players; number of matches, goals, shots and cards are stored throughout a player's career. a screenshot is attached.
don't count on much more in 1.9.0 though.
vector, friend, come down to earth databases...
gyözö
don't count on much more in 1.9.0 though.
vector, friend, come down to earth databases...
gyözö
- Attachments
-
- Career values in the extended player info view.
- career_values.jpg (6.55 KiB) Viewed 1085 times
Press any key to continue or any other key to quit.
na its boring therevector, friend, come down to earth Wink databases...
well im not sure about linux db but in windows it would be a no brainer to implement. in fact chips was already doing this a while back..(he didnt realise bygfoot had some similar reports) He was adding the data by hand....
I may even look at what linuxs db is like...
Well we will see about that.. all i need from you is the file/files that contain the histroy data and an explanation how you have saved the info.OpenOffice.org (http://www.openoffice.org) provides a near drop-in replacement for Microsoft Office.
extract said info from its xml format into something office can read and we will see.. Long term who knows.,,
of course wether or not everyone has access to office im not sure but it seems to come bundled with most linux distros nowadays?
signed "off planet enterprises"
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?
I had a quick look at openoffice and the one thing that isnt up to scratch is the db side ;( They are working hard on it but its not as easy as "ms access" so in this light there is no point in pursuing such extravagance.
at this point in time anyrate
at this point in time anyrate
"There are two ways to score. Dribble it over the line or smash it into the back of the net."
What type are you?
What type are you?