What's up, RMers? - Printable Version+- Save-Point (https://www.save-point.org)
+-- Forum: Games Development (https://www.save-point.org/forum-4.html)
+--- Forum: Development Discussion (https://www.save-point.org/forum-17.html)
+--- Thread:
What's up, RMers? (/thread-395.html)Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
RE: What's up, RMers? - DerVVulfman - 10-04-2026
(Yesterday, 04:20 AM)DerVVulfman Wrote: The second a sort of RMXP scripts database rewrite based on the old RMXP SDK. But for that, I am using kyonides's HiddenChest system as it is using a much newer version of Ruby so it is definitely more compliant with newer versions of RUBY. The old SDK focused mostly on initialization and the main update methods in the scene classes... but ignored much anything else. LOTS to break down where would-be scripters could comparatively attach code much easier.
Funny thing when you actually work to slice and dice the default scripts that the original team of the RMXP SDK of 2006-2008 didn't finish break into smaller sections.
I found this in Scene_Battle.
def start_phase4
# Shift to phase 4
@phase = 4
# Turn count
$game_temp.battle_turn += 1
# Search all battle event pages
for index in 0...$data_troops[@troop_id].pages.size
# Get event page
page = $data_troops[@troop_id].pages[index]
# If this page span is [turn]
if page.span == 1
# Clear action completed flags
$game_temp.battle_event_flags[index] = false
end
end
# Set actor as unselectable
@actor_index = -1
@active_battler = nil
# Enable party command window
@party_command_window.active = false
@party_command_window.visible = false
# Disable actor command window
@actor_command_window.active = false
@actor_command_window.visible = false
I'm sorry. The comment/description says the party command window is being ENABLED? # Shift to phase 4
@phase = 4
# Turn count
$game_temp.battle_turn += 1
# Search all battle event pages
for index in 0...$data_troops[@troop_id].pages.size
# Get event page
page = $data_troops[@troop_id].pages[index]
# If this page span is [turn]
if page.span == 1
# Clear action completed flags
$game_temp.battle_event_flags[index] = false
end
end
# Set actor as unselectable
@actor_index = -1
@active_battler = nil
# Enable party command window
@party_command_window.active = false
@party_command_window.visible = false
# Disable actor command window
@actor_command_window.active = false
@actor_command_window.visible = false
HAHAHA! Yeah, whoever was translating the original Japanese comments to English.... missed a spot.Now when I say I am breaking down the scripts... er...
def make_skill_action_result
# Get skill
@skill = $data_skills[@active_battler.current_action.skill_id]
# If not a forcing action
unless @active_battler.current_action.forcing
# Exit if unable to use due to SP running out
return if make_skill_action_result_blocked?
end
# Apply cost
make_skill_action_cost
# Refresh status window
@status_window.refresh
# Set Skill/Item actions
make_object_action_effects(@skill)
# Apply skill effect
make_skill_action_effect
end
# Get skill
@skill = $data_skills[@active_battler.current_action.skill_id]
# If not a forcing action
unless @active_battler.current_action.forcing
# Exit if unable to use due to SP running out
return if make_skill_action_result_blocked?
end
# Apply cost
make_skill_action_cost
# Refresh status window
@status_window.refresh
# Set Skill/Item actions
make_object_action_effects(@skill)
# Apply skill effect
make_skill_action_effect
end
I invite you to look at the original method from RPGMaker's Scene_Battle. Its a bit larger.
For this, I made several smaller methods
- make_skill_action_result_blocked? Which determines if a skill can be used or not...
- make_skill_action_cost Which reduces the attacker's SP cost
- make_object_action_effects Which updates the help, sets the animations, common events and targets (also used by Items)
- make_skill_action_effect Which finally performs the Game_Battler attack effects on the target(s)
Being broken into smaller sections makes adding new content (script addons) easier as rewriting the base method will likely not be needed.
The old RMXP SDK had a couple of good ideas; standarization on script method names, smaller and more manageable methods which would allow more compliance with other works, a means to optimize the code so systems automatically update without needs to be called.
They just sucked at marketing as they kept making updates after updates after updates, so when you made your SDK script it was immediatly broken by the NEXT version. I'm gong to work a bit on this... and see what tricks I can retrieve whilst keeping the XP naming standards.
.... this is just one of the many things I have been working upon...