Simulation Kit : The Revival

Taking the suggestion of not tying down a player to a single tournament for the sake of overall statistics, few updates have been made.

(a) Addition of sub-menus
sub_menu1.gif



(b) Filters - add
player_management_add_filter.gif



(c) Filters - remove
player_management_remove_filter.gif
 
May be I am asking too much here, but can we rate same player differently for different formats?... One player profile and 3 different rating according to different format... :p:D
 
May be I am asking too much here, but can we rate same player differently for different formats?... One player profile and 3 different rating according to different format... :p:D
You spoke my mind. I was about to ask you guys about ratings. As things stand, player creation would be a 2-step process. One would the base list (where only the player name, nationality, batting/bowling hand and role will be defined and will act as a bank)

The next set of attributes (ratings, bowler style, mentality etc) would be assigned based on tournaments/leagues. So when you start a new league, you first select a player from the bank (thereby avoiding having to create a player again) and then add the remaining attributes based on the format of the leauge (ODI,T20 or Test/FC).

Is that what you were looking for?
 
You spoke my mind. I was about to ask you guys about ratings. As things stand, player creation would be a 2-step process. One would the base list (where only the player name, nationality, batting/bowling hand and role will be defined and will act as a bank)

The next set of attributes (ratings, bowler style, mentality etc) would be assigned based on tournaments/leagues. So when you start a new league, you first select a player from the bank (thereby avoiding having to create a player again) and then add the remaining attributes based on the format of the leauge (ODI,T20 or Test/FC).

Is that what you were looking for?
That will be cool... :thumbs
 
The next set of attributes (ratings, bowler style, mentality etc) would be assigned based on tournaments/leagues. So when you start a new league, you first select a player from the bank (thereby avoiding having to create a player again) and then add the remaining attributes based on the format of the leauge (ODI,T20 or Test/FC).
If only the professors could have such kinda example of data abstraction! Ah, learning a lot with your work here. :)
 
You spoke my mind. I was about to ask you guys about ratings. As things stand, player creation would be a 2-step process. One would the base list (where only the player name, nationality, batting/bowling hand and role will be defined and will act as a bank)

The next set of attributes (ratings, bowler style, mentality etc) would be assigned based on tournaments/leagues. So when you start a new league, you first select a player from the bank (thereby avoiding having to create a player again) and then add the remaining attributes based on the format of the leauge (ODI,T20 or Test/FC).

Is that what you were looking for?
Or when we first create a player we add the attributes then only as base and then add modifiers for different format something like cricket coach.
 
Or when we first create a player we add the attributes then only as base and then add modifiers for different format something like cricket coach.
Haven't used cricket coach so I'm unsure how that system works. But it all depends on what the majority want. I'm fine with either way.
 
@asprin

Please see if the following is do able:
1. Add a save or resim option after match simulation (only saved matches stats are saved)
2. Tournament setup - instead of double round robin and knockouts etc. Just add a number of games to be played for any given tournament. This will give the league manager ample leeway to setup any type of tournament/league

PS. Are you going to allow commentary lines to be added by users?
 
1. Add a save or resim option after match simulation (only saved matches stats are saved)
2. Tournament setup - instead of double round robin and knockouts etc. Just add a number of games to be played for any given tournament. This will give the league manager ample leeway to setup any type of tournament/league

PS. Are you going to allow commentary lines to be added by users?

1. Will be easier for limited overs but challenging for Test/FC matches. Can't comment on it at the moment as I haven't reached that part yet
2. Actually yes, I concur. This is better approach as the manager can add the playoffs/semi-finals/finals in the match count as well.

Reg commentary lines, yes, that is the aim. Need to decide how to provide a platform for them to do so though - either via SimKit itself or an external page.
 
@asprin Somethings that might assist irt commentary and other. Somethings I put together while working with Parth.

DISMISSALS
Code:
Retired
Bowled
Caught
LBW
Run out
Stumped
FIELDING
Code:
Wicket-keeper
Close catching
Infield
Outfield
FIELDING POSITIONS

CLOSE CATCHING
Code:
Wicket-keeper
First slip
Second slip
Third slip
Leg slip
Leg gully
Short leg
Silly mid-on
Silly mid-off
Silly point
Gully

INFIELD
Code:
Short Fine leg
Backward Square leg
Square leg
Mid-wicket
Mid-on
Mid-off
Extra Cover
Cover
Point
Backward point
Short third man
Fly slip
OUTFIELD
Code:
Long stop
Deep fine leg
Long leg
Deep square leg
Deep midwicket
Cow corner
Long on
Straight hit
Long off
Deep extra cover
Deep cover
Deep point
Deep backward point
Third man

BATTING
Code:
Hand:
Left    
Right  
Position:
Top order (1-3)
Middle order (4-7)
Tail (8-11)
Code:
BATSMAN RATINGS
Run-machine
Class player
Specialist batsman
Recognised batsman
Plucky tail-ender
Rabbit
BOWLING
Code:
Slow
Leg-spin
Off-spin
Medium  
Medium-fast
Fast
Code:
BOWLER RATINGS
Spearhead
Strike bowler
Stock bowler
Part-time
Occasional
Non-bowler
Code:
${bowler}
the name of the bowler.
${striker}
the name of the batsman on strike.
${non_striker}
the name of the batsman who is not on strike.
${fielder}
the name of the fielder who catches, drops or fields the ball.
${position}
the name of the fielding position for the fielder.
${keeper}
the name of the wicket keeper.
${toss_winner}
the name of the team who won the toss.
${toss_decision}
'field' or 'bat' depending on what the team who won the toss decided to do first.
${batting_team}
the name of the batting team.
${bowling_team}
the name of the bowling team.
${shot_noun}
the name of the shot played (e.g. 'drive').
${shot_third_person}
third person verb form of the shot played (e.g. 'drives').
${shot_past}
past verb form of the shot played (e.g. 'driven').
BATTING
  • LEAVE
  • FRONT FOOT
  • BACK FOOT
Code:
Orthodox strokeplay:
Defensive shot
Leg glance
Flick
Hook
Pull
On drive
Straight drive
Off drive
Cover drive
Square drive
Square cut
Sweep
Cut
Late cut
Code:
Unorthodox strokeplay:
Reverse sweep
Slog and slog sweep
Upper cut
Switch hit
Scoop / ramp

Batsman Classifications:

Batsman Type: <Shot selections>
HTML:
Orthodox
Unorthodox
Balanced > Plays Orthodox and Unorthodox strokes
HTML:
Technical <Plays more grounded shots>
Radical <Plays more lofted shots>
Master blaster <Plays grounded and lofted shots equally well>
Rattings:
HTML:
Run-machine
Class player
Specialist batsman
Recognised batsman
Plucky tail-ender
Rabbit

Orthodox Technical Run-machine (Example: Hashim Amla) > hits more 4's
Unorthodox Radical Run-machine (Example: Glenn Maxwell) > hits for 6's
Balanced Master blaster Run-machine (Example: Virat Kohli / AB De Villiers) > hits 4's and 6's

The lower the batsman's ratting the fewer strokes in his arsenal.
 
Haven't used cricket coach so I'm unsure how that system works. But it all depends on what the majority want. I'm fine with either way.
If I remember correctly it was like this
Suppose a batsmen is rated 60 in list A which acted as a base. He is more of a longer format expert than short format.
First class modifier could be between 5-15 range while t20 modifier could be 0-(-15).

Regarding commentary I think it should be external so you can moderate it or else who knows all commentary lines could be Lynch Asprin.
 
Suppose a batsmen is rated 60 in list A which acted as a base. He is more of a longer format expert than short format.
First class modifier could be between 5-15 range while t20 modifier could be 0-(-15)
So this looks like it covers the best of both worlds - have a base point system when creating a player and then add extra points depending on the format the player is playing. But I'm thinking of making the base points non-editable once set (since it could affect ongoing leagues hosted by some another manager and this player turns out to be a part of it). Set once and forget. Otherwise create a new player if it needs to be changed/updated.

Regarding commentary I think it should be external so you can moderate it or else who knows all commentary lines could be Lynch Asprin.
Commentary will always be moderated, cannot risk leaving it as it is. And I'll have 3-levels of approval for your userid :p
 
So this looks like it covers the best of both worlds - have a base point system when creating a player and then add extra points depending on the format the player is playing. But I'm thinking of making the base points non-editable once set (since it could affect ongoing leagues hosted by some another manager and this player turns out to be a part of it). Set once and forget. Otherwise create a new player if it needs to be changed/updated.


Commentary will always be moderated, cannot risk leaving it as it is. And I'll have 3-levels of approval for your userid :p
By locking the attributes we may have a problem, as sometimes a league manager have upgrades in leagues.
Maybe instead of everyone using the same player, every user get an instance/copy of the player on their own account where the changes won't affect the player for everyone.
 

Users who are viewing this thread

Top