Why Extension Plugins Are Not Standalone - Revision history

Yanfly at 16:01, 30 September 2021

2021-09-30T16:01:58Z

2021-09-30T15:31:44Z

2021-09-30T15:20:58Z

‎Cost Reduction

2021-09-30T15:16:08Z

‎Cost Reduction

2021-09-30T15:09:24Z

2021-09-30T14:40:28Z

2021-09-30T14:40:15Z

‎So Why Do People Complain About Cores?

2021-09-30T14:39:28Z

2021-09-30T14:27:14Z

2021-09-30T14:17:05Z

‎Why We Create Extension Plugins

@@ Line 230: / Line 230: @@
 We would suggest that you [https://forums.rpgmakerweb.com/index.php?categories/classifieds.55/ find a programmer to commission].
 They would need to create the code from scratch, make sure it works standalone, and maintain it with your other plugins for your game.
 |}

@@ Line 203: / Line 203: @@
 The same applies for plugins.
 === Maintenance ===
-Text
+Plugin maintenance is a massively overlooked component when it comes to the development of plugins.
 |}

@@ Line 188: / Line 188: @@
 Naturally, the cost of these games would be a lot more expensive than if they were just cartridges that can be swapped out across a median game console, right?
 The same works with Extension Plugins and their Cores.
-The development time (and therefore cost) of an extension plugin is usually far less than if it were to be developed as a standalone.
+The development time (and therefore cost) of an Extension Plugin is usually far less than if it were to be developed as a standalone.
-The code doesn't have to be made in such a way where it has to be self sufficient.
+The code doesn't have to be made in such a way where it has to be self sufficient because that code already exists in the Cores.
 === Maintenance ===

@@ Line 181: / Line 181: @@
 === Cost Reduction ===
-Text
+Imagine if every time you wanted to buy a new game, you had to buy an entirely new console for it.
+Pokemon Yellow came with its own Game Boy and can only be played with that specific Game Boy.
 === Maintenance ===

@@ Line 144: / Line 144: @@
 I cannot answer that.
 However, I can only guess that the reason why people complain about "Cores" is when they install Convenience Cores and don't see any changes to their games, major or minor.
 |}

← Older revision		Revision as of 14:40, 30 September 2021
Line 74:		Line 74:


−	==== "But not everybody wants all of those features!" ====	+	=== "But not everybody wants all of those features!" ===

	And that's why we included options to disable them.		And that's why we included options to disable them.

@@ Line 134: / Line 134: @@
 The convenience isn't directed towards the game dev, but instead, towards the plugin dev.
 They contain functions that allow the plugin dev to quickly parse notetags, shuffle arrays, or the like.
-While on the surface, it seems "helpful", the problem is that these Cores offer very little changes to the game project itself.
+While on the surface, it seems "helpful", the issue most users have is that these Cores offer very little changes to the game project itself.
 I've almost never seen people argue about the dependency on VisuStella MZ's [[Core Engine VisuStella MZ|Core Engine]].

@@ Line 90: / Line 90: @@
-=== Why We Create Extension Plugins ===
+== Why We Create Extension Plugins ==
 [[File:ExtStandalone_Extension.jpg|300px]]
 When features get too big and complex to be toggleable to work with Cores, we turn them into Extension Plugins (Tier 3) instead.
 Extension Plugins are purely '''optional''' features that aren't necessary for the core traditional RPG experience.
@@ Line 104: / Line 106: @@
 The Extension Plugins (and selected System Plugins) expand upon the base to which the Core Plugins offer.
 This is to maintain the modularity of the plugin library and game engine while keeping the cores strong but flexible.
 Previously with my '''RPG Maker VX''' libraries, I rarely was able to go past 30 to 50 scripts per library unless they were completely small scripts that were more like tweaks.
 However, a script library of tweaks doesn't create a full game engine.
 Instead, to expand past that and to create a proper game engine, the concept of core scripts/plugins and extension scripts/plugins had to be made.
 This is why '''Yanfly Engine Ace''' script library for '''RPG Maker VX Ace''' was able to scale past 100 scripts.
 It is also the same reason why [[Yanfly Engine Plugins]] for '''RPG Maker MV''' was able to reach 200 plugins.
 This is also the reason why '''VisuStella MZ''' for '''RPG Maker MZ''' is able to scale to the size it is today.
 |}

@@ Line 34: / Line 34: @@
 [[File:ExtStandalone_Core.jpg]]
-This section will answer two things: Why we create cores and why we created them the way we did for VisuStella MZ.
+This section will answer two things: Why we create Core Plugins (Tier 1) and why we created them the way we did for VisuStella MZ.
 === The Purpose of Cores ===
@@ Line 94: / Line 94: @@
 [[File:ExtStandalone_Extension.jpg|300px]]
-When features get too big and complex to be toggleable to work with Cores, we turn them into Extension Plugins instead.
+When features get too big and complex to be toggleable to work with Cores, we turn them into Extension Plugins (Tier 3) instead.
 |}