Having at last got around to buying a copy of !Spark, I intend to
download this to the Stuttgart archive. I would really like some feedback
on the game, if you can send email you can email me at work as:
dxc@ast.cam.ac.uk
The game has mostly been tested on an A5000 running Riscos 3.0. I have
had trouble running a cut-down version of this under Riscos 2.0, it runs
on an A3020 running Riscos 3.1, although slowly. Somebody please tell me
whether it works on a RiscPC.
This version asks two questions when it starts up. The first is
whether you want Text or Graphics startup screens. Graphics Screens
use SYS "Font_Paint", this has caused me problems on some machines, but
if you can use it it looks nicer. If the fonts look speckled, try altering
sub-pixel anti-aliasing in the Fonts setup with !Configure.
The second question is whether you want High or Low resolution sprites.
High resolution is mode 27, low is mode 12. Mode 12 is twice as fast. On
an A5000 mode 27 is fine, on a slower machine you may need to use mode 12.
If you don't have a multi-sync monitor you will definitely need mode 12.
If you decide that you can always use graphics screens and high resolution,
comment out the line PROCGetscreentype at about line 220.
I would be interested to hear from anyone with one of the Basic compilers
as to whether it will compile.
Please send comments to me, please send any changes you make to the code
to me, if you are an artist and you want to redraw sprites please do so,
and if you think they are any good please send then to me as well. Many
of the current sprites were drawn by my children. If you have any
modification you think is worthwhile PLEASE TELL ME. I will of course
acknowledge you if I include it in a future release.
Notes for !Cricket release 1.35 - August 1993.
!Cricket is a limited overs cricket game for one or two players. The original
version was written on an A5000 using Mode 27 graphics, there is also a
version for Mode 12 (!Cricket12). If you distribute this programme please
distribute both versions, along with this message. The program was written
by myself, with suggestions and help with the sprites from Mr. S.D. Carter,
Mr. N.J. Carter and Mr. P.A. Carter. Some improvements to the text questions
and input were made by Mr. M.P. Wall. It is being placed in the Public Domain
and may be distributed without charge. However if you do find the program
useful, and you think that you would have been prepared to pay for it, you
are invited to make a donation (I suggest £7:50) to:-
World Vision of Britain,
Dychurch House,
8 Abington Street,
Northampton, NN1 2AJ.
World Vision run child sponsorship programmes, and projects to provide
children in the third world with food and education, so your donation really
would be worthwhile.
If you have already donated £5 to World Vision for the use of Cricket
version 1.1 vould you please send them another £2:50 for the use of this
version, which is substantially enhanced
If you distribute this program, please do not modify it before doing so.
However for your own use I am happy for you to modify the parameters set
in the Procedure PROCInitialscreen, which is near to the end of the code.
These parameters determine how hard the ball is hit, how it slows up on the
ground, how quickly the ball comes down if you hit it in the air, how fast
the bowler bowls, and how hard the fielders throw the ball in. If you find
the game too slow you may wish to increase some or all of these parameters.
INSTRUCTIONS
!Cricket is basically a game for two players. On the startup screen you can
enter the names of the players, and decide how many overs each player can
bat for. I suggest that you choose a fairly small number (like 10) until
you are used to the game. Each player in turn can bat until either he has
used up this number of overs, or he has lost 10 wickets. If the second
player passes the score of the first player then the game will end after the
end of the over in which he passes that score. At the end of the game the
winner is the player who has scored the most runs, or if the scores are
equal the winner is the player who has lost the least wickets.
A major enhancement of this version is the ability to name the players in
your team, and to assign them as types of bowlers, and as right or left
handed batsmen. There is also a choice of four sets of sprites to
represent the colour of the players, three are supposed to look like
European, Southern Asian and West Indian players respectively. The fourth
set of sprites has been added recently, they are supposed to look like
Shane Warne. In addition to the total number of overs, you can assign the
maximum number per bowler.
There are representative test teams for England, India, Pakistan, Australia
and the West Indies; I entered these in early 1993, and already they may
be out of date, but they are easy to change. In the setup screen an item is
normally changed by pressing the left mouse button over it, but to change
the character of a player (e.g. colour or type of bowling) press the right
button over the player.
There are three levels of difficulty, Easy, Medium, and Difficult. The
choice of level affects only how long the batsman has to hit the ball;
the harder the level the more critical the timing of the shot.
There are also three speed settings, Slow, Medium and Fast. Fast seems much
too fast (for me at least) on an A5000, while Slow is too slow on an A3000.
There are a few extra problems with the graphics at the fast speeds (shadows
being left where they shouldn't be). If the game is too slow even at fast
speed, then try the MODE 12 version.
Before the start the innings, and between of overs, the player who is not
batting has the opportunity to set the field. A fairly standard field is set
at the start, and this can be changed to cut off the batsman's favourite
shots. To move a fielder, place the pointer over the fielder you want to
move, and select him with the RIGHT mouse button. There will be a beep, and
in the lower left corner of the screen the number and name of the fielder
will appear. Then move the pointer to where you want to put the fielder, and press the MIDDLE button. There will be a different beep, and the fielder willmove. You cannot move a fielder too close to the pitch; too close to the
bowler's runup; between the stumps and the wicketkeeper; too close to another
fielder; or outside the boundary. There is no check that the resulting field
position is legal, for instance you can place more than two fielders behind
square on the leg side. You cannot move the wicketkeeper or the bowler.
By selecting the Bowler icon in the lower left corner, the fielding captain
can chose another bowler. He cannot choose the bowler who bowled the last
over, or a bowler who has bowled his maximum number of overs. If he does
not change bowlers, then the bowler who bowled the last over but one will
continue. If this bowler has used up his overs, then the program will go
directly into change bowler mode at the end of the over. Bowlers whose
names appear in blue can be selected, the one who is selected appears in
red. Bowlers whose names appear in brown cannot be selected for some
reason.
Fast bowlers bowl faster but straighter, with a medium or slow bowler the
ball will deviate more off the pitch. The fast bowlers will also bowl
occasional bouncers, which are often possible to hit for six, but with the
risk of being caught in the outfield.
Version 1.5 has five possible venues: England, India, Jamaica, Australia
and South Africa. The sprites are different, and so are the characteristics
of the pitch. In India, the spin bowlers get more spin. In England the
medium pace bowlers can move the ball away from the bat more. In Australia
and Jamaica, the fast bowlers are faster, and in Jamaica they bowl twice
as many bouncers.
The player who is batting should now take over. When you are ready press the
LEFT mouse button, and the bowler will run in and bowl.
In addition to the main side on view of the game, there is an end on view
from the batsman's perspective, on the right hand side of the screen. The
batting player should watch this as the bowler bowls.
When the ball hits the pitch it may deviate either way. The batsman should
use the end on view to decide whether to hit the ball, and if so which way.
The batsman can hit the ball with any mouse button. To hit the ball to the
left (leg side for a right handed batsman; off side for a left handed
batsman) use the LEFT button, to hit it to the right use the RIGHT button,
and to hit it straight use the MIDDLE button. However if the ball deviates
off the pitch it will not go exactly where you want it, as it will not come
off the middle of the bat. The strength of the shot also depends upon the
direction that ball deviates, the shot will have more power if you hit with
the movement of the ball. If the ball deviates sharply, and you try to hit
it, it is possible that you may edge the ball, and it will go in the air
towards the slip or short leg fielders. These fielders almost always
catch the ball. If the ball does deviate sharply to the off side, or to the
leg side as well if the bowler is medium or slow, then the batsman should
not hit it.
The timing of the shot is important too. If the ball is hit early it will go
in the air. In this case it may go for 6, but it may be caught by an
outfielder. If the ball is hit when it has reached the batsman then it
will go along the ground, which is safer. If the ball is hit into the
outfield, whether along the ground or in the air, then the batsmen can run.
To make the batsmen run, press a mouse button other than the one used to hit
the ball. For instance, if the ball was hit on the leg side by pressing the
LEFT mouse button, press the RIGHT or MIDDLE button to make the batsmen run.
the batsmen can start another run at any time until the fielder has thrown
the ball toward the wicketkeeper, but beware, because the fielders throw the
ball in hard and accurately, and if it reaches the wicketkeeper before the
batsmen have made their ground then you will be run out.
There is a random element in the velocity of the ball off the bat when
attempting to hit the faster bowlers, this was introduced at version 1.35
because it appeared to be too easy to slog the fast bowlers straight back
over their heads.
If the batsman does not hit the ball, and it does not deviate off the pitch,
then he will be bowled. The umpire will signal a 4, 6, or a wicket, and the
scoreboard in the top right corner will be updated before the bowler bowls
again.
If a fielder has caught the ball press the LEFT mouse button to make him
throw it in. If the ball is in the wicketkeeper's gloves the press the LEFT
button to make the bowler bowl the next ball.
While the second player is batting his target will be shown on a small
scoreboard in the lower left corner. The scores of the individual batsmen
are shown in the lower right.
It is also possible to play a one player game, or to play without naming
your teams. In this case the game reverts to a simpler mode of operation,
with a right handed batsmen only, and a simple choice of Fast, Medium and
Spin bowlers at the start of each over.
PARAMETERS (Set in PROCInit, modified in PROCInitialscreen)
angle The viewing angle of the main field of play.
angle2 The viewing angle of the small end on view of the pitch.
initialheight The height at which the bowler carries the ball.
batheight The height of the centre of gravity of the bat. This affects
the vertical angle when it is hit in the air. Reducing this
makes the ball go straight up in the air.
vdrag The rate at which the ball slows down when hit along the
ground.
vball0 How hard the ball is hit, both along the ground and in the
air. There are also random and direction dependent
components to the velocity of each individual shot.
accball The downward acceleration when the ball is hit in the air.
vsnick0 The velocity of the ball after it is edged. This also has
a random component.
vthrow The speed at which the fielders throw the ball in
vbowler% The speed at which the bowler bowls. This is an integer.
freqrun% The number of movements of the ball per 2 movements of the
batsmen. Reduce this to speed the batsmen up, but not below
2.
freqfielder% The number of movements of the ball per movement of the
fielder chasing the ball. Again, don't reduce this below
2.
KNOWN BUGS
When the fielder gets near the ball and picks it up the batsmen slow down,
due to the number of graphics calls at that time.
Occasional confusion as to which sprite should be in front when two overlap
(particularly the umpire and the bowler, when the bowler is moving to field
the ball).
Fielders seem confused about where the ball is going when it bounces.
However this isn't too unlike real fielders in the kind of cricket I
play. If the wicketkeeper goes for a catch and doesn't get to it then
he panics, and runs back to his stumps, and another fielder has to go
and fetch the ball.
Fielders run backwards in an unrealistic way, they should run backwards
for short distances only.
Bowler stops with arm up after bowling, rather than following through.
When there are two batsmen of different sprite types, then their types
are the wrong way round on even numbered runs (second and fourth).
FUTURE ENHANCEMENTS
Alternate overs from opposite ends.
I would appreciate any comments, reports of further bugs, and suggestions
