Custom Game Over behavior

じ☆ve冰风

Custom Game Over

Version 1.3.2

by McKathlin
​

Introduction
    Change what happens when the party dies or an event calls Game Over processing.

    In some games, after the party dies they find themselves in a recently visited safe place, where they can continue their game with all experience and progress intact, but some money or items lost. With Custom Game Over, you can have party death cause something similar to that, or something completely different!

Features

• New: Set a common event to run when the party dies, before the fade to game over.
  
• Choose whether or not the Game Over Screen shows first.
  
• Choose whether to reload from the last save.
  
• Set a common event to run after game over, instead of going back to the title screen.
  

How to Use
    Download or copy this plugin, and save it inside your project's js\plugins folder as Kath_GameOver.js -- The filename is important, because the plugin manager refers to it when retrieving the plugin parameters. Add and enable it in the plugin manager, as you would with any other plugin. It should function properly regardless of where it's placed in the plugin list.

    This plugin offers parameters that accept common events by their ID. First create a common event in the database, take note of its ID, then go to the plugin manager and enter that ID number for the value of the common event parameter you would like to set.

    Your Party Death Common Event will run in the same scene that the party dies, in place of a standard Game Over. If the party dies in battle, then this common event will play out in battle, unless the common event explicitly calls a scene change command (such as the Game Over command).

    Your After Game Over Common Event can do practically anything you want. The default post-Game-Over state is dark and silent to provide a blank slate for the common event to work from. At minimum, you'll need to make sure that your After Game Over Common Event includes the following commands:

• Transfer Player
  
• Fadein Screen
  

    Everything else you add is up to you.

Full Help Text

Spoiler                Code:       

1. This plugin is designed to play well by itself and with other plugins.
2. There are no known conflicts, but conflict is possible with other plugins
3. that directly alter Game Over behavior.
5. ================================
6. = Party Death Common Event ID  =
7. ================================
8. Assigning a Party Death Common Event replaces the usual Game Over scene
9. call with a common event call. This lets you (the game designer) make
10. something happen instead of (or before) the standard Game Over screen.
11. Open the database to Common Events to find the ID of the common event
12. to call on party death, and enter this ID number as the parameter.
13. Here are some pointers:
14. * The Party Death common event will run in the same scene where the party
15.   was just defeated. If the party died in battle, the common event will run
16.   in battle, right after the party-is-defeated message and music effect.
17.   So if you want to make something happen after a slow fadeout
18.   and return to the map, I recommend using the After Game Over Common Event
19.   instead.
20. * Using the Abort Battle command in your Party Death Common Event will
21.   interfere with scene control, so do not use the Abort Battle command
22.   in a Party Death Common Event that also uses the Game Over command.
23. * If you would like the Game Over screen (or a fadeout and cut to the map
24.   if "Show Game Over Scene" is false) to show at the end of your common
25.   event, remember to use the Game Over command in your common event.
26.   Avoiding the Game Over screen is easy: avoid calling the Game Over command.
27. * Directly calling the Game Over command from any event will still show
28.   the Game Over screen normally (unless you've set Show Game Over Scene to
29.   false). To force your custom party death behavior, use a command that
30.   calls your party death common event instead.
32. =========================
33. = Show Game Over Scene  =
34. =========================
35. RPG Maker's default behavior takes the player to Scene_GameOver on
36. party death or on a scene processing call to Scene_GameOver.
37. This processing shows a Game Over screen.
38. After the player sees the screen and presses any key,
39. the game exits to the title screen.
41. If Show Game Over Scene is set to false, player will see a fade to black
42. before going to the next scene. This will be the case regardless of whether
43. Game Over state is reached by party death or by a direct command in an event.
45. Whether or not the Game Over screen shows, which scene is next depends on
46. whether the After Game Over Common Event is set, and what it is set to.
48. ====================
49. = Reload Last Save =
50. ====================
51. Set Reload Last Save to true to make the game automatically reload from its
52. most recent save on game over. If a Game Over Common Event is specified,
53. the reload occurs before the common event is reserved. If no common event
54. is given, then the reload happens instead of going to the title screen.
56. If Reload Last Save is true but the player has not yet saved,
57. then the player is returned to the Title Screen.
59. ====================================
60. = After Game Over Common Event ID  =
61. ====================================
62. Assigning a After Game Over common event makes gameplay continue after
63. the party loses, instead of RPG Maker's default behavior of returning the
64. party to the title screen. Open the database to Common Events to find the
65. ID of the common event to call on game over, and enter this ID number as
66. the parameter.
68. In the content of the common event, the game designer can customize what
69. happens when the party dies or reaches an event-dictated Game Over state.
70. The After Game Over common event might do some of the following things:
71. * Take away gold and/or items
72. * Return the player to a safe place
73. * Restore HP to one or more party members
74. * Have the party's rescuer say something
75. * ...anything that suits this game!
77. IMPORTANT: When control flows to the Game Over common event,
78. the screen will start blacked out. This gives the event time to handle
79. transfers and other processing before showing the player the screen.
80. Once those things are ready, remember to fade in!
82. The After Game Over Common Event (AGOCE) differs from the Party Death Common
83. Event (PDCE) in the following ways:
84. * The PDCE runs instead of or before the Game Over screen or fadeout;
85.   the AGOCE runs after the Game Over scene or fadeout completes.
86. * The PDCE only automatically replaces Game Overs caused by party death.
87.   The AGOCE autoruns after all Game Overs, regardless of their cause.
88. * The PDCE runs in the same scene where party death occurred.
89.   The AGOCE runs in a newly started map scene, with the screen faded to
90.   black, and the party leader revived to 1 HP.

复制代码

Script

Spoiler                Code:       

1. //=============================================================================
2. // Custom Game Over, version 1.3.2
3. // by McKathlin
4. // Kath_GameOver.js
5. // Last Update: 2024-10-07
6. //=============================================================================
8. /*:
9. * @plugindesc Change what happens when the party dies or Game Over is called.
10. *
11. * @param Party Death Common Event ID
12. * @desc The ID of the common event to run as soon as the party dies.
13. * Leave blank to fade immediately to Game Over.
14. * @default
15. *
16. * @param Show Game Over Scene
17. * @desc Whether to show Scene_Gameover. If false, only a brief fade to black is seen.
18. * @default true
19. *
20. * @param Reload Last Save
21. * @desc If true, reload from last save instead of title screen,
22. * or before common event, if any.
23. * @default false
24. *
25. * @param After Game Over Common Event ID
26. * @desc The ID of the common event to run AFTER the Game Over scene (or fadeout).
27. * Leave blank to go to title.
28. * @default
29. *
30. * @help This plugin is designed to play well by itself and with other plugins.
31. * There are no known conflicts, but conflict is possible with other plugins
32. * that directly alter Game Over behavior.
33. *
34. * ================================
35. * = Party Death Common Event ID  =
36. * ================================
37. * Assigning a Party Death Common Event replaces the usual Game Over scene
38. * call with a common event call. This lets you (the game designer) make
39. * something happen instead of (or before) the standard Game Over screen.
40. * Open the database to Common Events to find the ID of the common event
41. * to call on party death, and enter this ID number as the parameter.
42. * Here are some pointers:
43. * * The Party Death common event will run in the same scene where the party
44. *   was just defeated. If the party died in battle, the common event will run
45. *   in battle, right after the party-is-defeated message and music effect.
46. *   So if you want to make something happen after a slow fadeout
47. *   and return to the map, I recommend using the After Game Over Common Event
48. *   instead.
49. * * Using the Abort Battle command in your Party Death Common Event will
50. *   interfere with scene control, so do not use the Abort Battle command
51. *   in a Party Death Common Event that also uses the Game Over command.
52. * * If you would like the Game Over screen (or a fadeout and cut to the map
53. *   if "Show Game Over Scene" is false) to show at the end of your common
54. *   event, remember to use the Game Over command in your common event.
55. *   Avoiding the Game Over screen is easy: avoid calling the Game Over command.
56. * * Directly calling the Game Over command from any event will still show
57. *   the Game Over screen normally (unless you've set Show Game Over Scene to
58. *   false). To force your custom party death behavior, use a command that
59. *   calls your party death common event instead.
60. *
61. * =========================
62. * = Show Game Over Scene  =
63. * =========================)
64. * RPG Maker's default behavior takes the player to Scene_GameOver on
65. * party death or on a scene processing call to Scene_GameOver.
66. * This processing shows a Game Over screen.
67. * After the player sees the screen and presses any key,
68. * the game exits to the title screen.
69. *
70. * If Show Game Over Scene is set to false, player will see a fade to black
71. * before going to the next scene. This will be the case regardless of whether
72. * Game Over state is reached by party death or by a direct command in an event.
73. *
74. * Whether or not the Game Over screen shows, which scene is next depends on
75. * whether the After Game Over Common Event is set, and what it is set to.
76. *
77. * ====================
78. * = Reload Last Save =
79. * ====================
80. * Set Reload Last Save to true to make the game automatically reload from its
81. * most recent save on game over. If a Game Over Common Event is specified,
82. * the reload occurs before the common event is reserved. If no common event
83. * is given, then the reload happens instead of going to the title screen.
84. *
85. * If Reload Last Save is true but the player has not yet saved,
86. * then the player is returned to the Title Screen.
87. *
88. * ====================================
89. * = After Game Over Common Event ID  =
90. * ====================================
91. * Assigning a After Game Over common event makes gameplay continue after
92. * the party loses, instead of RPG Maker's default behavior of returning the
93. * party to the title screen. Open the database to Common Events to find the
94. * ID of the common event to call on game over, and enter this ID number as
95. * the parameter.
96. *
97. * In the content of the common event, the game designer can customize what
98. * happens when the party dies or reaches an event-dictated Game Over state.
99. * The After Game Over common event might do some of the following things:
100. * * Take away gold and/or items
101. * * Return the player to a safe place
102. * * Restore HP to one or more party members
103. * * Have the party's rescuer say something
104. * * ...anything that suits this game!
105. *
106. * IMPORTANT: When control flows to the Game Over common event,
107. * the screen will start blacked out. This gives the event time to handle
108. * transfers and other processing before showing the player the screen.
109. * Once those things are ready, remember to fade in!
110. *
111. * The After Game Over Common Event (AGOCE) differs from the Party Death Common
112. * Event (PDCE) in the following ways:
113. * * The PDCE runs instead of or before the Game Over screen or fadeout;
114. *   the AGOCE runs after the Game Over scene or fadeout completes.
115. * * The PDCE only automatically replaces Game Overs caused by party death.
116. *   The AGOCE autoruns after all Game Overs, regardless of their cause.
117. * * The PDCE runs in the same scene where party death occurred.
118. *   The AGOCE runs in a newly started map scene, with the screen faded to
119. *   black, and the party leader revived to 1 HP.
120. */
122. var Imported = Imported || {};
123. Imported.Kath_GameOver = true;
125. //=============================================================================
126. // Helper method: parseBoolean
127. //=============================================================================
128. var Kath = Kath || {};
129. Kath.Core = Kath.Core || {};
131. // Convert a user-entered string into a Boolean true or false value.
132. Kath.Core.parseBoolean = function(parameter, defaultValue) {
133.     switch (String(parameter).trim().toLowerCase()) {
134.         case 'true':
135.         case 't':
136.         case 'yes':
137.         case 'y':
138.         case 'on':
139.         case '1':
140.             return true;
141.         case 'false':
142.         case 'f':
143.         case 'no':
144.         case 'n':
145.         case 'off':
146.         case '0':
147.             return false;
148.         default:
149.             return defaultValue;
150.     } // end switch
151. };
153. //=============================================================================
154. // Parameters and Constants
155. //=============================================================================
157. Kath.Parameters = PluginManager.parameters('Kath_GameOver');
158. Kath.Param = Kath.Param || {};
160. Kath.Param.PartyDeathCommonEventID =
161.     Number.parseInt(Kath.Parameters['Party Death Common Event ID']);
162. Kath.Param.ShowGameOverScene =
163.     Kath.Core.parseBoolean(Kath.Parameters['Show Game Over Scene'], true);
164. Kath.Param.ReloadLastSave =
165.     Kath.Core.parseBoolean(Kath.Parameters['Reload Last Save'], false);
166. Kath.Param.AfterGameOverCommonEventID =
167.     Number.parseInt(Kath.Parameters['After Game Over Common Event ID']);
169. Kath.GameOver = {};
170. Kath.GameOver.RELOAD_FADE_DELAY = 60;
172. //=============================================================================
173. // Party death common event
174. //=============================================================================
176. // Replacement method
177. // Like original, but with handling added for Party Death Common Event case.
178. BattleManager.processDefeat = function() {
179.     this.displayDefeatMessage();
180.     this.playDefeatMe();
181.     if (this._canLose) {
182.         this.replayBgmAndBgs();
183.         this.endBattle(2);
184.     } else {
185.         AudioManager.stopBgm();
186.         if (Kath.Param.PartyDeathCommonEventID) {
187.             $gameParty.reviveLeader();
188.             $gameTemp.reserveCommonEvent(Kath.Param.PartyDeathCommonEventID);
189.             $gameTroop.setupBattleEvent(); // Run the reserved common event.
190.             // the battle doesn't end here in this case,
191.             // unless a scene control command ends it in the common event.
192.         } else {
193.             this.endBattle(2);
194.         }
195.     }
196. };
198. // replacement method
199. Scene_Base.prototype.checkGameover = function() {
200.     if ($gameParty.isAllDead()) {
201.         if (Kath.Param.PartyDeathCommonEventID) {
202.             $gameParty.reviveLeader();
203.             $gameTemp.reserveCommonEvent(Kath.Param.PartyDeathCommonEventID);
204.         } else {
205.             SceneManager.goto(Scene_Gameover);
206.         }
207.     }
208. };
210. Game_Party.prototype.reviveLeader = function() {
211.     if ($gameParty.isAllDead()) {
212.         $gameParty.leader().setHp(1);
213.         $gameParty.leader().clearStates();
214.     }
215. };
217. //=============================================================================
218. // Skip Game Over Scene
219. // Redefine several methods of Scene_GameOver
220. // so that it skips straight to the next scene.
221. //=============================================================================
223. if (!Kath.Param.ShowGameOverScene) {
224.     Scene_Gameover.prototype.create = function() {
225.         Scene_Base.prototype.create.call(this);
226.         //this.playGameoverMusic(); // No music.
227.         this.createBackground();
228.     };
230.     Scene_Gameover.prototype.start = function() {
231.         Scene_Base.prototype.start.call(this);
232.         //this.startFadeIn(this.slowFadeSpeed(), false); // No fadein.
233.     };
235.     Scene_Gameover.prototype.update = function() {
236.         // Do not require a trigger.
237.         if (this.isActive() && !this.isBusy()) {
238.             this.gotoTitle();
239.         }
240.         Scene_Base.prototype.update.call(this);
241.     };
243.     Scene_Gameover.prototype.createBackground = function() {
244.         // Load image to avoid potential conflicts.
245.         this._backSprite = new Sprite();
246.         this._backSprite.bitmap = ImageManager.loadSystem('GameOver');
247.         //this.addChild(this._backSprite); // But don't show it!
248.     };
249. }
251. // new method
252. Kath.GameOver.findPostGameOverSceneClass = function() {
253.     if (Kath.Param.ReloadLastSave) {
254.         if (DataManager.isThisGameFile(DataManager.lastAccessedSavefileId())) {
255.             return Scene_Map;
256.         } else {
257.             return Scene_Title;
258.         }
259.     } else if (Kath.Param.AfterGameOverCommonEventID) {
260.         return Scene_Map;
261.     } else {
262.         return Scene_Title;
263.     }
264. };
266. //=============================================================================
267. // After-Game-Over behavior. This includes reload last save, if called for.
268. //=============================================================================
270. if (Kath.Param.ReloadLastSave) {
271.     // extended method
272.     Kath.GameOver.Scene_Gameover_gotoTitle = Scene_Gameover.prototype.gotoTitle;
273.     Scene_Gameover.prototype.gotoTitle = function() {
274.         var saveId = DataManager.lastAccessedSavefileId();
275.         if (!DataManager.isThisGameFile(saveId)) {
276.             // This game hasn't been saved yet. Go to the title screen.
277.             return Kath.GameOver.Scene_Gameover_gotoTitle.call(this);
278.         }
279.         DataManager.loadGame(saveId);
280.         $gamePlayer.requestMapReload();
281.         $gameScreen.startFadeOut(1); // start next scene blacked out
282.         if (Kath.Param.AfterGameOverCommonEventID > 0) {
283.             $gameTemp.reserveCommonEvent(Kath.Param.AfterGameOverCommonEventID);
284.             SceneManager.goto(Scene_Map);
285.         } else {
286.             SceneManager.goto(Scene_Map);
287.             // Transfer to where we are, to set BGM, map fadein, etc.
288.             $gamePlayer.reserveTransfer($gameMap.mapId(),
289.                 $gamePlayer.x, $gamePlayer.y, $gamePlayer.direction(), 0);
290.             $gameScreen.startFadeIn(this.slowFadeSpeed());
291.         }
292.     };
293. } else if (Kath.Param.AfterGameOverCommonEventID > 0) {
294.     // replacement method
295.     Scene_Gameover.prototype.gotoTitle = function() {
296.         $gameScreen.startFadeOut(1); // start next scene blacked out
297.         $gameParty.reviveLeader();
298.         $gameTemp.reserveCommonEvent(Kath.Param.AfterGameOverCommonEventID);
299.         SceneManager.goto(Scene_Map);
300.     };
301. }

复制代码

Download here: Kath_GameOver.js

Version History
Version 1.0.1 - Minor edits to Version 1.0, mostly in help text.

Version 1.0.2 - Show/Skip Game Over Screen bugfix attempted, but found to cause the game to freeze on some machines.

Version 1.0.3 - Show/Skip Game Over Screen feature removed for now.

Version 1.1 - Show/Skip Game Over Screen feature is back. The bug appears to be fixed.

Version 1.2 - New parameter allows you to reload data from the player's last save

Version 1.3 - Set the Party Death Common Event to customize what happens before (or instead of!) the Game Over fadeout.

Version 1.3.2 - Added a note to the help text to avoid using "Abort Battle" and "Game Over" commands in the same Party Death Common Event.

FAQ

Q: I've set a common event to occur after Game Over, but when I try it, the screen stays black and I can't see anything. Help!
A: After Game Over, the screen starts out faded to black to give the After Game Over Common Event a chance to handle transfers and other "behind-the-scenes" processing before showing the screen. To get rid of the blackness, make sure to run a "Fade In" command as part of your After Game Over Common Event.

Q: My game lets the player continue exactly where they left off after they die. But when they continue, the music for the map they're in doesn't autoplay like it's supposed to. Is this a bug, or do I need to do something differently?
A: This is not a bug. The silence gives the Game Over common event a chance to run its course without being interrupted by the BGM of the map where the player died. A transfer will cause the music of the destination to autoplay. Though you don't need the player to go anywhere, transferring the player to where they already are will fix your music problem. Here's how to do it:

• At the start of your Game Over common event, use the Control Variables command three times to assign three variables: the player's current map ID, X coordinate, and Y coordinate.
  
• Place a Player Transfer command at the part of the event when the map's BGM should start playing.
  
• As always, remember to use a Fadein Screen command!  (The fade that accompanies the Player Transfer command won't cut it.)
  

Terms of Use
    This plugin is free for all use, including commercial use. Please credit me (McKathlin) where appropriate. Sending me a free copy of your completed game is encouraged but not required.


本贴来自国际rpgmaker官方论坛作者:McKathlin处,因国际论坛即将永久关站,为了存档多年珍贵资料,署名转载到本论坛存档,由于官方帖子为英文原帖，需要中文翻译请点击论坛顶部切换语言为中文就可以将帖子翻译成中文浏览,方便大家随时查看,原文地址：https://forums.rpgmakerweb.com/threads/custom-game-over-behavior.55072/