fig1 is a block diagram of a game system according to an embodiment of the present invention . the game system according to the present embodiment includes a game server 1 and a plurality of communication terminals 2 . for the sake of simplicity , only one communication terminal 2 is illustrated in fig1 . the game server 1 transmits a battle game to the communication terminal 2 . in the explanation below , a user in this game forms a deck from a maximum of 12 cards by combining cards within the game . each card has a command determining an action of the player character controlled by the user . the user battles with an enemy character , i . e . an opponent , by selecting a card included in the deck as a command to determine the action of the player character . a battle takes place when a predetermined battle event occurs within the game , such as when the player character encounters an enemy . the game server 1 includes a server communication unit 10 , a storage unit 11 , a procedure determination unit 12 , an auto mode processing unit 13 , a winning reward determination unit 14 , and a server control unit 15 . the server communication unit 10 communicates with the communication terminal 2 over either or both of a wireless and wired connection . the storage unit 11 stores user data 110 , an opponent database ( db ) 111 , a battle history 112 , and a battle log 113 . with reference to fig2 ( a ) and 2 ( b ) , the user data 110 is described . the user data 110 ( 110 a , 110 b ) is unique information for each user and includes a variety of information necessary to play the battle game . as illustrated in fig2 ( a ) , the user data 110 a includes the parameters “ level ”, “ experience ”, “ maximum deck cost ”, and “ money ” in association with a “ user id ” that uniquely identifies a user . the user data 110 a may also include information such as a list of cards or a list of game items held by the user . the “ user id ” may be a character string , a player character name that the user freely sets , or the like that can uniquely identify a user . the “ level ” is a parameter indicating the degree of development of the player character within the game . a higher numerical value for the level indicates a higher degree of development . “ experience ” is a parameter that contributes to an increase in level and increases in accordance with progress in the game , battles , and the like . when experience reaches 100 %, the level rises , and experience is reset to 0 %. the “ maximum deck cost ” is a parameter contributing to the degree of freedom for forming the deck . as described below , a “ cost ” is set for each card , and the user must form the deck so that the total cost of all the cards in the deck is equal to or less than the maximum deck cost . accordingly , the maximum deck cost is the maximum value of the total cost of cards that can be included in the deck . the maximum deck cost increases as the level rises . “ money ” is a parameter indicating the amount of game currency that the user has . money increases in accordance with progress in the game , battles , and the like . the user data 110 b includes information on the deck that the user has formed . as illustrated in fig2 ( b ) , the user data 110 b includes the following parameters for each card constituting the user &# 39 ; s deck : “ card id ”, “ level ”, “ experience ”, “ evolution ”, “ cost ”, “ hp ”, “ atk ”, “ command id ”, “ command type ”, and “ activation / recovery turns ”. the “ card id ” is information that can identify a card within the game and may be any character string , a character name depicted on the card , or the like that can uniquely identify a card . the “ level ” is a parameter indicating the degree of development of the card . a higher numerical value for the level indicates a higher degree of development . “ experience ” is a parameter that contributes to an increase in level and increases in accordance with progress in the game , battles , and the like . “ evolution ” is a parameter indicating the number of times that evolution is possible with a predetermined method such as synthesizing a card of the same type . “ evolution ” is indicated as “ current evolution level / final evolution level ”. for example , if “ evolution ” is “ ⅓ ”, this indicates that evolution is possible two more times . “ cost ” is a parameter indicating the cost necessary to include the card in the deck . “ hp ” is a parameter contributing to the hit points ( hp ) of the player character and increases in accordance with level and evolution . the maximum hp value for the player character is the total of the hp of each card in the deck . the player character &# 39 ; s hp decreases when , for example , the player character is attacked by an opponent in a battle , and the player character loses the battle when hp reaches zero . “ atk ” is a parameter contributing to the power of s player character actions via commands such as attack , recover , and the like . the power of a command increases as the atk value is higher . the “ command id ” is information that can identify a command that a card has and may , for example , be any character string or any command name that can uniquely identify a command . the “ command type ” is information indicating the type of the corresponding command . for example , command types include “ attack ”, which inflicts damage on an opponent , “ recover ”, which recovers the player character &# 39 ; s hp , “ assist ”, which for example strengthens / weakens the player character / opponent , and the like . “ activation / recovery turns ” is a parameter indicating the time required from when a card is selected at the start of the turn until the action due to the command is performed ( number of turns to activation ) and the time required from when the action due to the command is performed until the card can be selected again ( number of turns to recovery ). “ activation / recovery turns ” is indicated as “ number of turns to activation / number of turns to recovery ”. for example , if the user starts a turn by selecting “ card001 ” that includes “ cmd01 ” for which the “ activation / recovery turns ” is “ ½ ”, the player character attacks the opponent with the command “ cmd01 ” one turn after card selection , i . e . in the turn immediately after selection of the card . the user then cannot select “ card001 ” again until two turns after selection of the card , i . e . until one more turn has passed after completion of the turn in which the player character attacks with the command “ cmd01 ”. note that a turn is an opportunity for the player character and the opponent to act . at the start of a turn , the user selects a card to determine the action of the player character , and the turn progresses . when the player character and all of the opponents that can act in a turn have acted , or when there is no player character nor opponent who can act in the turn , then the turn finishes , and a new turn begins . next , with reference to fig3 ( a ) and 3 ( b ) , the opponent database 111 is described . the opponent database 111 ( 111 a , 111 b ) includes a variety of information related to the enemy characters that become opponents . as illustrated in fig3 ( a ) , the opponent database 111 a includes the parameters “ level ”, “ hp ”, “ atk ”, “ command id ”, “ command type ”, and “ activation / recovery turns ” in association with an “ enemy character id ” that can uniquely identify an enemy character . since these parameters are the same as the card parameters described for the user data 110 b , a description thereof is omitted . an enemy character may have a plurality of commands , for example as “ enemy002 ” does . when the enemy character has a plurality of commands , one of the commands is automatically selected , and the enemy character acts . as illustrated in fig3 ( b ) , the opponent database 111 b includes combinations of enemy character ids that appear as opponents in association with “ opponent sets ”. specifically , at the start of a battle in the game , one of the opponent sets is selected from the opponent database 111 b to determine the opponent . for example , when “ set01 ” is selected as the “ opponent set ”, three of “ enemy001 ” appear as opponents . in other words , the “ opponent set ” is an identifier indicating a combination of enemy characters that constitute the opponent ( s ). next , with reference to fig4 , the battle history 112 is described . the battle history 112 is information related to opponents with whom the user has battled in the past . specifically , in association with a user id , the battle history 112 includes “ battled opponent sets ”, i . e . the opponent sets ( identifiers ) of opponents with whom the user has battled in the past , and includes win - loss information on the user for each battled opponent set . for example , in fig4 , “ user001 ” has won against opponents corresponding to “ set01 ” and “ set02 ”, and the win - loss information indicates “ win ”. furthermore , “ user001 ” has not won against the opponent corresponding to “ set03 ”, and the win - loss information indicates “ loss ”. next , “ user002 ” has won against the opponent corresponding to “ set02 ”, and the win - loss information indicates “ win ”. on the other hand , “ user002 ” has not won against the opponent corresponding to “ set03 ”, and the win - loss information indicates “ loss ”. furthermore , “ user002 ” has not battled against the opponent corresponding to “ set01 ”, and hence “ set01 ” is not included in the “ battled opponent set ”. next , with reference to fig5 , the battle log 113 is described . the battle log 113 is information indicating the content of a battle when the battle is conducted in the below - described auto mode . specifically , the battle log 113 includes a “ turn number ”, “ acting character ”, and “ content of action ”. the battle log 113 may be temporarily stored in the storage unit 11 and erased after completion of the battle process . the “ turn number ” indicates each turn that occurred from the start to the end of a battle . the “ acting character ” indicates the id of each player character and enemy character that acted in the turn indicated by the turn number . the “ content of action ” indicates the result of the action taken by the corresponding acting character . for example , fig5 shows that in the “ first turn ”, “ user001 ” attacked via “ cmd01 ” and inflicted 1000 points of damage on “ enemy001a ”. note that fig5 shows an example of the opponent being three of “ enemy001 ”, differentiated from each other by being listed as “ enemy001a ”, “ enemy001b ”, and “ enemy001c ”. the explanation now returns to fig1 . for each battle taking place in the game , the procedure determination unit 12 determines a procedure for conducting the battle to be either a manual mode ( first mode ) for conducting the battle based on user operations and an auto mode ( second mode ) for conducting the battle with fewer user operations than in the manual mode . conducting the battle with fewer user operations than in the manual mode includes , for example , the cases of conducting the battle semi - automatically by omitting a portion of command selection by the user and conducting the battle automatically by omitting all command selection by the user . specifically , at the start of a battle in the game , the procedure determination unit 12 looks up the opponent set selected as the opponent in the battle history 112 . the procedure determination unit 12 judges whether the opponent set matches a battled opponent set , included in the battle history 112 , for which the win - loss information is “ win ”, i . e . whether the user has battled the opponent in the past and won . when the opponent set matches a battled opponent set for which the win - loss information is “ win ”, i . e . when the user has won against the opponent in the past , then upon acquiring an input signal from the communication terminal 2 , the procedure determination unit 12 determines the procedure for conducting the battle based on the input signal . the input signal is for a user operation that the communication terminal 2 has received on the below - described mode selection screen 3 or confirmation screen 4 . on the other hand , when the opponent set does not match a battled opponent set for which the win - loss information is “ win ”, i . e . when the user has not won against the opponent in the past , then the procedure determination unit 12 determines the procedure for conducting the battle to be the manual mode and transmits an instruction to the communication terminal 2 to conduct the battle in manual mode . the auto mode processing unit 13 performs a battle process in auto mode . specifically , the auto mode processing unit 13 automatically controls the player character , selecting cards and attacking the opponent in accordance with a predetermined process . one possible predetermined process is , for example , to use only the cards included in the deck for which the command type is attack and to attack in order starting with the first enemy character . any other process , however may be used . for example , when the recovery is turn becomes longer as the power of the command is higher , then the battle may be conducted by prioritizing use of cards having commands with a long recovery turn . until the battle ends , i . e . until the hp of either every opponent or of the player character reaches zero , the auto mode processing unit 13 continues to attack and calculates the battle result . the battle result includes whether the battle was a win or a loss and the remaining hp of the player character . the auto mode processing unit 13 then stores the content of the battle in auto mode in the storage unit 11 as the battle log 113 . before the communication terminal 2 is caused to display the below - described mode selection screen 3 , i . e . before the user selects the procedure for conducting the battle , the auto mode processing unit 13 preferably performs the above - described process to calculate the battle result by auto mode as a predicted result . when the procedure determination unit 12 determines that the procedure for conducting the battle is auto mode , the auto mode processing unit 13 then determines the calculated predicted result to be the battle result of the battle . when the player character wins the battle , the winning reward determination unit 14 determines a winning reward in the game and provides the winning reward to the user . specifically , the winning reward determination unit 14 judges whether the user has won the battle based on the battle result calculated by the auto mode processing unit 13 or on the battle result acquired from the communication terminal 2 . when the user has won the battle , the winning reward determination unit 14 then determines the winning reward by a predetermined method and provides the winning reward to user . the winning reward determination unit 14 preferably determines the winning reward in accordance with the procedure for conducting the battle . for example , the winning reward for a battle in manual mode may be selected from a reward group with a higher value than the winning reward for a battle in auto mode . the server control unit 15 controls the various operations of the game server 1 and the overall conduction of the game . the server control unit 15 also determines the opponent with whom the user battles . specifically , at the start of a battle in the game , the server control unit 15 selects an opponent set from the opponent database 111 b and determines the selected opponent set to be the opponent . via the server communication unit 10 , the server control unit 15 transmits an instruction to the communication terminal 2 to display a variety of game screens . the variety of game screens include , for example , the below - described mode selection screen 3 , confirmation screen 4 , auto mode rendering screen 5 , battle result screen 6 , battle log screen 7 , reward attainment screen 8 , and manual mode battle screen 9 . the communication terminal 2 is provided with a terminal communication unit 20 , a display unit 21 , an operation unit 22 , a manual mode processing unit 23 , and a terminal control unit 24 . the terminal communication unit 20 communicates with the game server 1 over either or both of a wireless and wired connection . the display unit 21 outputs display pertaining to the game provided by the game server 1 . specifically , the display unit 21 displays the below - described mode selection screen 3 , confirmation screen 4 , auto mode rendering screen 5 , battle result screen 6 , battle log screen 7 , reward attainment screen 8 , and manual mode battle screen 9 . any type of display device may be used in the display unit 21 , such as a liquid crystal display , organic el display , or the like . the operation unit 22 receives user operations for the game . the operation unit 22 transmits an input signal in accordance with the received user operation to the terminal control unit 24 . any input interface may be used in the operation unit 22 , such as a button , touch panel , or the like . in the following explanation , the operation unit 22 is assumed to be a touch panel . the manual mode processing unit 23 performs a battle process in manual mode . specifically , the manual mode processing unit 23 displays the below - described manual mode battle screen 9 on the display unit 21 and conducts the battle based on user operations . once the battle ends , the manual mode processing unit 23 determines the battle result and transmits the battle result to the game server 1 via the terminal communication unit 20 . the terminal control unit 24 controls the various operations of the communication terminal 2 . also , upon acquiring an input signal from the operation unit 22 in accordance with a user operation received on one of the various screens displayed on the display unit 21 , the terminal control unit 24 transmits the input signal to the game server 1 via the terminal communication unit 20 . next , with reference to fig6 ( a ) and 6 ( b ) , the mode selection screen 3 is described . the mode selection screen 3 is a screen for causing the user to select between the manual mode and the auto mode as the procedure for conducting the battle . at the start of a battle in the game , when the user has battled the opponent in the past , the mode selection screen 3 is displayed on the display unit 21 of the communication terminal 2 . information in accordance with the predicted result of the battle calculated by the auto mode processing unit 13 of the game server 1 is preferably displayed on the mode selection screen 3 . the information in accordance with the predicted result is information suggestive of the battle result when conducting the battle in auto mode . specifically , as illustrated in fig6 ( a ) , when the predicted result for example corresponds to “ can win with remaining hp of at least 80 % and less than 100 %”, then “ you can easily win !” is the displayed information . on the other hand , if the predicted result corresponds to “ can &# 39 ; t win ”, then “ this is quite a tough opponent . . . ” is the displayed information . as illustrated in fig6 ( b ) , the mode selection screen 3 includes a character icon 30 , message displaying area 31 , manual button 32 , and auto button 33 . the character icon 30 is the image of a character that presents the information displayed in the message displaying area 31 to the user . the message displaying area 31 is an area displaying a comment encouraging the user to select a procedure for conducting the battle and displaying information in accordance with the predicted result of the battle . specifically , when for example the predicted result is “ can win with at least 80 % and less than 100 % of hp remaining ”, then “ you &# 39 ; ve battled this enemy before , and you can win easily ! which way will you fight ?” is displayed in the message displaying area 31 . the manual button 32 is an input interface that receives a user operation for selecting the manual mode as the procedure for conducting the battle . once the user taps the manual button 32 , the display switches to the below - described manual mode battle screen 9 . the auto button 33 is an input interface that receives a user operation for selecting the auto mode as the procedure for conducting the battle . once the user taps the auto button 33 , the display switches to the below - described confirmation screen 4 or auto mode rendering screen 5 . next , with reference to fig7 , the confirmation screen 4 is described . the confirmation screen 4 is a confirmation screen for the user to confirm selection of the auto mode on the mode selection screen 3 . the confirmation screen 4 is displayed on the display unit 21 of the communication terminal 2 when the predicted result is more adverse for the user than a predetermined standard and the user has selected the auto mode on the mode selection screen 3 . the predetermined standard may be set freely by the game provider or the like and may , for example , be a standard value relating to the remaining hp of the player character after the battle . in this case , a predicted result that is advantageous for the user indicates that the remaining hp is at least the standard value . conversely , a predicted result that is adverse for the user indicates that the remaining hp is less than the standard value . in this way , for example by setting the predetermined standard to be “ remaining hp 50 %”, the confirmation screen 4 is displayed when the remaining hp in the predicted result is less than 50 % of the maximum hp and the user has selected auto mode on the mode selection screen 3 . as illustrated in fig7 , the confirmation screen 4 includes a character icon 40 , a message displaying area 41 , a manual button 42 , and an auto button 43 . since the character icon 40 , manual button 42 , and auto button 43 are respectively similar to the character icon 30 , manual button 32 , and auto button 33 in the mode selection screen 3 , a description thereof is omitted . the message displaying area 41 is an area displaying a comment encouraging the user to confirm selection of auto mode on the mode selection screen 3 despite the fact that the predicted result is a battle result that is more adverse for the user than the predetermined standard . specifically , “ you don &# 39 ; t stand a chance of winning this way . . . your only hope is to fight the battle yourself . will you ?” is displayed in the message displaying area 41 . next , with reference to fig8 , the auto mode rendering screen 5 is described . the auto mode rendering screen 5 is a screen presenting the user with a rendition of the battle in auto mode . the auto mode rendering screen 5 includes a displaying area 50 for the enemy character name , a displaying area 51 for enemy character images , and a displaying area 52 for the deck . the displaying area 50 for the enemy character name is an area for displaying the enemy character id of the enemy character that is the opponent and the number of that enemy character that appears . the displaying area 51 for enemy character images is an area for displaying the image of each enemy character that is the opponent . the displaying area 52 for the deck is an area for displaying images of the plurality of cards included in the user &# 39 ; s deck . as a rendition of a battle in auto mode , the displaying area 52 for the deck moves towards the displaying area 51 for enemy character images . the displaying area 51 for enemy character images and the displaying area 52 for the deck then collide , and the entire screen turns white . display then switches to the below - described battle result screen 6 . as compared to the rendition of a battle with the below - described manual mode battle screen 9 , the rendition of a battle with the auto mode rendering screen 5 has a shorter display time and is a simpler rendition . hence , the processing load is smaller . next , with reference to fig9 , the battle result screen 6 is described . the battle result screen 6 is a screen presenting the user with the result of the battle in auto mode . the battle result screen 6 includes a displaying area 60 for the result , a displaying area 61 for the deck , a battle log button 62 , and a next button 63 . since the displaying area 61 for the deck is similar to the displaying area 52 for the deck , a description thereof is omitted . the displaying area 60 for the result is an area displaying whether the battle was won or lost . fig9 shows an example in which the user won the battle , and “ win ! !” is displayed in the displaying area 60 for the result . conversely , when the user loses the battle , for example “ lose . . . ” or the like may be displayed in the displaying area 60 for the result . the battle log button 62 is an input interface for receiving a user operation to display the content of the battle in auto mode . once the user taps the battle log button 62 , the display switches to the below - described battle log screen 7 . the next button 63 is an input interface for receiving a user operation to switch from the battle result screen 6 to the next screen . once the user taps the next button 63 , the display switches to the below - described reward attainment screen 8 . next , with reference to fig1 , the battle log screen 7 is described . the battle log screen 7 is a screen presenting the user with the battle log 113 that indicates the content of the battle in auto mode . the battle log screen 7 includes a displaying area 70 for the battle log and a close button 71 . the displaying area 70 for the battle log is an area for displaying the battle log 113 . by the user swiping the displaying area 70 for the battle log up and down , the entire battle log 113 can be displayed by scrolling . the close button 71 is an input interface for receiving a user operation to terminate display of the battle log screen 7 . once the user taps the close button 71 , the display switches to the battle result screen 6 . next , with reference to fig1 , the reward attainment screen 8 is described . the reward attainment screen 8 is a screen presenting the user with the winning reward provided to the user when the user has won the battle . the reward attainment screen 8 includes a displaying area 80 for the reward and an ok button 81 . the displaying area 80 for the reward is an area for displaying information related to the winning reward provided to the user . the information related to the winning reward includes , for example , an image of the game card or item that is the reward , a card id or an item id that can identify an item , and an acquisition count . by the user swiping the displaying area 80 for the reward up and down , the information relating to all of the winning rewards can be displayed by scrolling . the ok button 81 is an input interface for receiving a user operation to terminate the battle process . once the user taps the ok button 81 , the battle process terminates , and the display switches for example to the screen immediately before the start of a battle . next , with reference to fig1 , the manual mode battle screen 9 is described . the manual mode battle screen 9 is a screen for fighting a battle in manual mode . the manual mode battle screen 9 includes i ) a field area 90 a displaying a player character 91 , a displaying area 92 for player status , an enemy character 93 ( 93 a , 93 b , 93 c ), an enemy hp indicator 94 ( 94 a , 94 b , 94 c ), a number of enemy wait turns 95 ( 95 a , 95 b , 95 c ), and a target icon 96 , and ii ) a displaying area 90 b for the deck in which cards 97 ( 97 a , 97 b , 97 c , 97 d , 97 e ) are displayed . fig1 illustrates the state immediately before the start of a turn , i . e . the state of waiting for a user operation to determine the action of the player character 91 . the field area 90 a is an area for displaying graphics such as the player character 91 . the turn progresses once the user determines the action of the player character 91 , and a rendition is provided in the field area 90 a in accordance with the action of the player character 91 and the like . the player character 91 is a 2d or 3d graphic representing the player character that the user controls . the displaying area 92 for player status displays the remaining hp of the player character 91 numerically and with an indicator . each enemy character 93 ( 93 a , 93 b , 93 c ) is a 2d or 3d graphic representing an enemy character that is the opponent . each enemy hp indicator 94 ( 94 a , 94 b , 94 c ) indicates the remaining hp of the corresponding enemy character 93 . the number of enemy wait turns 95 ( 95 a , 95 b , 95 c ) indicates the number of turns until the corresponding enemy character 93 acts next . the target icon 96 indicates the target that the player character 91 is attacking . the user can change the attack target by tapping an enemy character 93 . the displaying area 90 b for the deck is an area for displaying cards 97 included in the user &# 39 ; s deck . by the user swiping the displaying area 90 b for the deck to the left and right , the card 97 of every card included in the deck can be displayed . the displaying area 90 b for the deck can preferably be minimized towards the bottom of the display screen . in this case , the entire manual mode battle screen 9 becomes the field area 90 a . each card 97 is displayed as a combination of a card image and an image indicating the command type of the command that the card has . at the start of each turn , the user selects one card from among selectable cards 97 to determine the action of the player character 91 . for example , in the state illustrated in fig1 , the card 97 a is selected if the user drags the card 97 a from the displaying area 90 b for the deck into the field area 90 a . the player character 91 then attacks the enemy character 93 a with the command that the selected card 97 a has . when a user cannot select a card 97 , such as during rendition of the battle , it is preferably made clear that the user cannot tap the cards 97 for example by darkening display of the cards 97 . next , with reference to fig1 , operations of the game server 1 according to the present embodiment are described . the flowchart in fig1 illustrates operations for a battle process performed by the game server 1 . this process begins when a predetermined battle event occurs , such as when the player character encounters an enemy . first , the server control unit 15 determines the opponent with whom the user battles ( step s 100 ). specifically , the server control unit 15 selects an opponent set from the opponent database 111 b and determines the selected opponent set to be the opponent . next , the procedure determination unit 12 judges whether the user has battled the opponent determined in step s 100 in the past and won ( step s 101 ). specifically , the procedure determination unit 12 looks up the opponent set determined in step s 100 in the battle history 112 . when the opponent set matches a battled opponent set that is included in the battle history 112 and for which the win - loss information is “ win ”, the procedure determination unit 12 judges that the user has won in the past ( step s 101 : yes ), and the process proceeds to step s 102 . conversely , when the opponent set does not match a battled opponent set that is included in the battle history 112 and for which the win - loss information is “ win ”, the procedure determination unit 12 judges that the user has not battled and won in the past ( step s 101 : no ), and the process proceeds to step s 110 . in step s 101 , when determining that the user has won in the past ( step s 101 : yes ), the auto mode processing unit 13 calculates the predicted result of the battle in auto mode ( step s 102 ). next , the server control unit 15 transmits an instruction to the communication terminal 2 to display the mode selection screen 3 ( step s 103 ). next , upon receiving from the communication terminal 2 an input signal for a user operation received on the mode selection screen 3 , the procedure determination unit 12 judges whether auto mode has been selected based on the input signal ( step s 104 ). when auto mode has been selected ( step s 104 : yes ), the process proceeds to step s 105 . conversely , when manual mode has been selected ( step s 104 : no ), the process proceeds to step s 110 . when auto mode has been selected in step s 104 ( step s 104 : yes ), the server control unit 15 judges whether the predicted result of the battle calculated in step s 102 is more adverse for the user than a predetermined standard ( step s 105 ). when the predicted result is more adverse than the predetermined standard ( step s 105 : yes ), the process proceeds to step s 106 . conversely , when the predicted result is at least the predetermined standard ( step s 105 : no ), the process proceeds to step s 108 . when the predicted result is more adverse than the predetermined standard in step s 105 ( step s 105 : yes ), the server control unit 15 transmits an instruction to the communication terminal 2 to display the confirmation screen 4 ( step s 106 ). next , upon receiving from the communication terminal 2 an input signal for a user operation received on the confirmation screen 4 , the procedure determination unit 12 judges whether auto mode has been selected based on the input signal ( step s 107 ). when auto mode has been selected ( step s 107 : yes ), the process proceeds to step s 108 . conversely , when manual mode has been selected ( step s 107 : no ), the process proceeds to step s 110 . when the predicted result is at least the predetermined standard in step s 105 ( step s 105 : no ), or when auto mode has been selected in step s 107 ( step s 107 : yes ), the auto mode processing unit 13 determines the predicted result calculated in step s 102 to be the battle result of the battle ( step s 108 ). next , the server control unit 15 transmits an instruction to the communication terminal 2 to display the auto mode rendering screen 5 ( step s 109 ). conversely , when judging in step s 101 that the user has not won in the past ( step s 101 : no ) or when manual mode is selected in step s 104 or step s 107 ( step s 104 : no , step s 107 : no ), the procedure determination unit 12 determines the procedure for conducting the battle to be manual mode and transmits an instruction to the communication terminal 2 to execute a battle process in manual mode ( step s 110 ). after step s 110 , the server control unit 15 waits until acquiring the battle result for manual mode from the communication terminal 2 ( step s 111 ), and upon acquisition of the battle result , the process proceeds to step s 112 . after step s 109 or step s 111 , the server control unit 15 transmits an instruction to the communication terminal 2 to display the battle result screen 6 ( step s 112 ). next , the server control unit 15 waits until acquiring from the communication terminal 2 an input signal for a user operation received by the communication terminal 2 on the battle result screen 6 ( step s 113 ). upon acquiring the input signal in step s 113 , the server control unit 15 then judges whether the input signal is an input signal via the battle log button 62 ( step s 114 ). when the input signal is an input signal via the battle log button 62 ( step s 114 : yes ), the process proceeds to step s 115 . on the other hand , when the input signal is an input signal via the next button 63 ( step s 114 : no ), the process proceeds to step s 116 . when the input signal in step s 114 is an input signal via the battle log button 62 ( step s 114 : yes ), the server control unit 15 transmits to the communication terminal 2 an instruction to display the battle log screen 7 ( step s 115 ). the process then returns to step s 113 and continues . on the other hand , when the input signal in step s 114 is an input signal via the next button 63 ( step s 114 : no ), the winning reward determination unit 14 judges whether the user has won the battle based on the battle result determined by the auto mode processing unit 13 in step s 108 ( step s 116 ). when the user has won ( step s 116 : yes ), the process proceeds to step s 117 . conversely , when the user has lost ( step s 116 : no ), the present process terminates . when the user has won in step s 116 ( step s 116 : yes ), the winning reward determination unit 14 determines a winning reward and provides the winning reward to the user ( step s 117 ). the winning reward determination unit 14 preferably determines the winning reward in accordance with the procedure for conducting the battle . the server control unit 15 then transmits an instruction to the communication terminal 2 to display the reward attainment screen 8 ( step s 118 ), and the process terminates . next , with reference to fig1 , operations of the communication terminal 2 according to the present embodiment are described . the flowchart in fig1 illustrates operations for a battle process performed by the communication terminal 2 . this process begins when a predetermined battle event occurs , such as when the player character encounters an enemy . first , the terminal control unit 24 waits for an instruction from the game server 1 and judges whether an instruction to execute a battle process in manual mode has been received ( step s 200 ). when an instruction for manual mode has been received ( step s 200 : yes ), the process proceeds to step s 209 . conversely , when an instruction for manual mode has not been received ( step s 200 : no ), the process proceeds to step s 201 . when an instruction for manual mode has not been received in step s 200 ( step s 200 : no ), the terminal control unit 24 receives an instruction to display the mode selection screen 3 from the game server 1 and displays the mode selection screen 3 on the display unit 21 ( step s 201 ). next , upon acquiring from the operation unit 22 an input signal for a user operation received on the mode selection screen 3 , the terminal control unit 24 transmits the input signal to the game server 1 ( step s 202 ). the terminal control unit 24 then waits for an instruction from the game server 1 and judges whether an instruction to execute a battle process in manual mode has been received ( step s 203 ). when an instruction for manual mode has not been received ( step s 203 : no ), the process proceeds to step s 204 . conversely , when an instruction for manual mode has been received ( step s 203 : yes ), the process proceeds to step s 209 . when an instruction for manual mode has not been received in step s 203 ( step s 203 : no ), the terminal control unit 24 waits for an instruction from the game server 1 and judges whether an instruction to display the confirmation screen 4 has been received ( step s 204 ). when an instruction to display the confirmation screen 4 has been received ( step s 204 : yes ), the process proceeds to step s 205 . conversely , when an instruction to display the confirmation screen 4 has not been received ( step s 204 : no ), the process proceeds to step s 208 . when an instruction to display the confirmation screen 4 has been received in step s 204 ( step s 204 : yes ), the terminal control unit 24 displays the confirmation screen 4 on the display unit 21 ( step s 205 ). next , upon acquiring from the operation unit 22 an input signal for a user operation received on the confirmation screen 4 , the terminal control unit 24 transmits the input signal to the game server 1 ( step s 206 ). the terminal control unit 24 then waits for an instruction from the game server 1 and judges whether an instruction to execute a battle process in manual mode has been received ( step s 207 ). when an instruction for manual mode has not been received ( step s 207 : no ), the process proceeds to step s 208 . conversely , when an instruction for manual mode has been received ( step s 207 : yes ), the process proceeds to step s 209 . when an instruction for manual mode has not been received in step s 207 ( step s 207 : no ), then upon receiving an instruction to display the auto mode rendering screen 5 from the game server 1 , the terminal control unit 24 displays the auto mode rendering screen 5 on the display unit 21 ( step s 208 ). conversely , when an instruction for manual mode has been received in step s 200 , step s 203 , or step s 207 ( step s 200 : yes , step s 203 : yes , step s 207 : yes ), the manual mode processing unit 23 performs a battle process in manual mode ( step s 209 ). next , once the battle ends , the manual mode processing unit 23 determines the battle result and transmits the battle result to the game server 1 ( step s 210 ). after step s 208 or step s 210 , upon receiving an instruction to display the battle result screen 6 from the game server 1 , the terminal control unit 24 displays the battle result screen 6 on the display unit 21 ( step s 211 ). next , upon acquiring from the operation unit 22 an input signal for a user operation received on the battle result screen 6 , the terminal control unit 24 transmits the input signal to the game server 1 ( step s 212 ). the terminal control unit 24 then judges whether the input signal acquired in step s 212 is an input signal via the battle log button 62 ( step s 213 ). when the input signal is an input signal via the battle log button 62 ( step 213 : yes ), the process proceeds to step s 214 . on the other hand , when the input signal is an input signal via the next button 63 ( step s 213 : no ), the process proceeds to step s 216 . when the input signal in step s 213 is an input signal via the battle log button 62 ( step s 213 : yes ), then upon receiving an instruction to display the battle log screen 7 from the game server 1 , the terminal control unit 24 displays the battle log screen 7 on the display unit 21 ( step s 214 ). next , the terminal control unit 24 waits for a user operation on the battle log screen 7 ( step s 215 ), and upon receipt of an input signal via the close button 71 from the operation unit 22 , the process returns to step s 211 and continues . on the other hand , when the input signal in step s 213 is an input signal via the next button 63 ( step s 213 : no ), the terminal control unit 24 waits for an instruction from the game server 1 and judges whether an instruction to display the reward attainment screen 8 has been received ( step s 216 ). when an instruction to display the reward attainment screen 8 has been received ( step s 216 : yes ), the process proceeds to step s 217 . conversely , when an instruction to display the reward attainment screen 8 has not been received ( step s 216 : no ), the process terminates . when an instruction to display the reward attainment screen 8 has been received in step s 216 ( step s 216 : yes ), the terminal control unit 24 displays the reward attainment screen 8 on the display unit 21 ( step s 217 ). the terminal control unit 24 then waits for a user operation on the reward attainment screen 8 ( step s 218 ), and upon receipt of an input signal via the ok button 81 from the operation unit 22 , the process terminates . as described above , according to the present embodiment , a battle history 112 that includes identifiers ( opponent sets ) of opponents with whom the user has battled is stored . based on the battle history 112 and on the identifier of the opponent with whom a battle begins , a procedure for conducting the battle in the battle game is determined to be either manual mode or auto mode , and the battle is conducted with the determined procedure . it is hence possible to change the procedure for conducting the battle in accordance with the user &# 39 ; s past battle experience . while maintaining the gaming aspect of a battle in manual mode , user operation can be made less troublesome during a battle in auto mode . furthermore , the user can efficiently battle in a short period of time in auto mode , thereby improving the user &# 39 ; s experience . according to the present embodiment , when the identifier of the opponent with whom the battle begins matches the identifier of an opponent included in the battle history 112 , the mode selection screen 3 allowing the user to select either manual mode or auto mode is displayed . conversely , when the identifier of the opponent with whom the battle begins does not match the identifier of an opponent included in the battle history 112 , the procedure for conducting the battle is determined to be manual mode . in this way , the gaming aspect of a battle in manual mode for an opponent that the user is battling for the first time can be maintained . at the same time , when the user has already battled an opponent and hence is highly likely to have lost interest , the user can choose to battle using an easy operation in auto mode , thereby improving the user &# 39 ; s experience . the identifier of the opponent may be the individual enemy character ids of the opponents or the opponent set that indicates a combination of opponents . for example , as in the above - described embodiment , using the opponent set as the identifier of the opponent allows for maintenance of the gaming aspect in manual mode even when the user has already won against the individual enemy characters , since the level of battle difficulty or the like varies due to a different number or combination of enemy characters . according to the present embodiment , the battle history 112 may further include win - loss information on the user for each opponent with whom the user has battled , and when the identifier of the opponent with whom the battle begins matches an identifier that is included in the battle history 112 and that identifies an opponent against whom the user has won , the mode selection screen 3 may be displayed . in this way , for an opponent against whom the user has won in the past , i . e . an opponent against whom the user is highly likely to win in a new battle , the user can choose to battle using an easy operation in auto mode , thereby improving the user &# 39 ; s experience . according to the present embodiment , the auto mode processing unit 13 calculates the predicted result of the battle in auto mode , and before determining the procedure for conducting the battle , displays information corresponding to the predicted result on the display unit 21 . in this way , by suggesting the battle result in auto mode to the user , the user can decide which procedure for conducting the battle to select based on the suggestion . according to the present embodiment , when the predicted result is more adverse for the user than a predetermined standard and the user has selected auto mode on the mode selection screen 3 , the confirmation screen 4 for the user to confirm selection of auto mode is displayed . it is thus possible to reduce the chance of an unintended adverse result , as when the user selects auto mode due to an erroneous operation or the like on the mode selection screen 3 . according to the present embodiment , when conducting the battle in auto mode , the battle log 113 indicating the content of the battle is stored , and the battle log screen 7 for presenting the battle log 113 to the user is displayed . even for a battle in auto mode , the user can therefore confirm the content of the battle , thus increasing the user &# 39 ; s degree of satisfaction . according to the present embodiment , the winning reward is determined in accordance with the procedure for conducting the battle , and the determined winning reward is provided to the user . for example , the winning reward for a battle in manual mode is selected from a reward group with a higher value than the winning reward for a battle in auto mode . by thus encouraging the user to battle in manual mode , for which the gaming aspect is greater , the user &# 39 ; s interest in the game can be enhanced . although the present invention has been described based on drawings and examples , it is to be noted that various changes and modifications will be apparent to those skilled in the art based on the present disclosure . therefore , such changes and modifications are to be understood as included within the scope of the present invention . for example , the functions and the like included in the various units and steps may be reordered in any logically consistent way . furthermore , units or steps may be combined into one or divided . for example , the determination of whether to display the mode selection screen 3 may be made based on any information related to the opponent . specifically , the mode selection screen 3 may be displayed when the player character &# 39 ; s level is at least a predetermined value higher than the level of the enemy character that is the opponent . furthermore , the opponent is not limited to being an enemy character and may be the player character of another user or the like . another example is how , when the user wins a battle in manual mode with a result more advantageous for the user than the predicted result of the battle in auto mode , the winning reward may be selected from a reward group with an even higher value than the normal winning reward for manual mode . the user is thus encouraged to consider battle strategy in manual mode , thereby enhancing the user &# 39 ; s interest in the game . yet another example is that the above - described processes performed by the game server 1 or the communication terminal 2 may be performed in cooperation by the game server 1 and the communication terminal 2 . for example , for a process to cause the communication terminal 2 to display a game screen , one possible configuration is for a portion of the screen ( such as the portion displaying an image in accordance with game progress ) to be a web display that is displayed based on data generated by the game server 1 , and another portion ( such as the portion displaying a menu or other fixed input interface ) to be a native display via a native application installed on the communication terminal 2 . 95 , 95 a , 95 b , 95 c : number of enemy wait turns
a non - transitory computer readable recording medium having stored thereon instructions to be executed on by a game server , the game server and corresponding method which cause the game server to perform the steps of : provide a networked multiplayer battle game over a network , storing a battle history including an identifier of an opponent with whom a user has battled in the multiplayer battle game ; determining , based on the battle history and an identifier of an opponent with whom a battle begins , a procedure for conducting the battle in the battle game to be one of a first mode for conducting the battle based on user operations and a second mode for conducting the battle with fewer user operations than in the first mode , and conducting the battle with the determined procedure .