Baseball game dev diary V0.5.2.202012032305 Prepping for pitchers

  1. Created a player class. No such thing as a record anymore. Chose Class over Structure due to some web page recommendation. Was reminded that when variables within classes are set to private, you can’t change them outside of that class. So created a Property for each variable within the class that uses the Get and Set commands to read and write the values in the instances of a class. The private variable starts with an underscore, the property is the same name without the underscore. This should make coding the main game much easier.
  2. Presently, properties are: id, last name, first name, primary position, secondary positions, player type, pitches thrown, energy, stamina and game status.
  3. Created 28 instances of players for each team (scaled back from 40 for now).
  4. Made the base buttons clickable and each calls a procedure that is designed to show info for the batter/runner, but only when base is occupied. Later on will disable the buttons (including batter) if base is not occupied (or in between batters in the case of the batter button). 
  5. Moved some button toggles into their own procedures (when start game and reset game are clicked, they now do the same thing; when end of game or after simming have button toggle procedures.



Comments

Post a Comment

Popular posts from this blog

V1.1.4.202103032300 Basic player creator, line score tidy up and additional play results, including errors

This was a pretty huge four days! Player creator: This idea came to me when I started wondering how I could fulfil my plan of creating 10,000 players at random, at the same time giving them realistic attributes. Added a separate form to generate players which can eventually be saved to database. Presently just generates attributes for contact and power vs L/R based on an entered minimum number of points to allocate, and entered maximum value for bonus points. Bonus points are calculated at random and added to total points to allocate across all attributes. If an attribute is already on 100, that bonus point is wasted. Works pretty well and will be expanded upon. Line score tidy up: This was something that was mostly a quick fix so I thought I may as well get it out of the way now. Now the button for the bottom of the current inning is disabled if playing the top of the inning. Now puts an X in the bottom of the 9th if not played at game end and disables tha...
Read more

MLB (Road to) The Show attribute progression

Image
Two key features of MLB The Show’s career mode have each divided its player base in two; satisfying one group of its users while alienating the other.  This first of two posts focuses on one of those features - the mode’s core feature of attribute progression. The proposed change will keep both groups of users satisfied without compromising the integrity of the mode. RPGs infiltrate the sport genre with career modes First introduced in MLB 07 The Show, Road to the Show (RTTS) is MLB The Show’s role-playing game (RPG) mode, which in sport games is often called career mode. We control a single character, whose existence (behaviours, skills and appearance) in its world is determined by a set of (mostly) numeric attributes. As the puppeteer of that character (and no other in the world) the attribute values are in our hands. It’s a difficult undertaking in sports games to implement a team-based career mode. Maintaining a balance between realism and keeping the player engage...
Read more

V1.1.5.202103211320 Fixing game log after dropped third strikes and errors

After analysing a whole simmed game, I identified several issues created by the inclusion of dropped third strikes and errors. It seemed that outs and baserunners were not being handled correctly. So as predicted, the logic didn’t work as intended. Also I realised that dropped third strikes were not actually errors so I had to stop them being recorded as such. Fixed dropped third strikes being recorded as errors and the text output to game log because of such. Moved the advanced to 3rd from 2nd (or 1st) and advanced to 2nd from 1st code that was in single, double, groundouts, flyouts, strikeouts (and would have been in many plays added later) to their own procedures ( CheckAdvanceTo3rd and CheckAdvanceTo2nd ). Will probably do the same with all runner movement to avoid duplication of code. Added text ‘advances to 3rd’ and ‘advances to 2nd’ to game log when such activity happens. This will help with debugging but also improve the user experience. Did this with two new Boole...
Read more