VisuStella MZ One Year Retrospective - Revision history

Yanfly: /* Negatives */

2021-12-18T02:29:55Z

‎Negatives

2021-08-13T04:39:15Z

‎Budget and Pricing Models

2021-08-13T04:33:23Z

‎Budget and Pricing Models

2021-08-13T04:32:21Z

‎Budget and Pricing Models

2021-08-13T04:23:23Z

‎Negatives

2021-08-13T04:23:11Z

‎Budget and Pricing Models

2021-08-13T04:22:33Z

‎Negatives

2021-08-13T04:13:50Z

‎Pricing Models

2021-08-13T04:01:25Z

‎Negatives

2021-08-13T04:00:25Z

@@ Line 291: / Line 291: @@
 They're given out to the RPG Maker community at a financial loss on our part.
-The next negative came in how we overstuffed the '''Wave'' bundles.
+The next negative came in how we overstuffed the '''Wave''' bundles.
 With the calculations made [[Why does VisuStella MZ cost more than RPG Maker MZ|here]], we can see that each Wave reduced the potential earnings of its set of plugins by 60% to 70%.
 It would have been more lucrative to put only 6 plugins per Wave instead of 8 to 10.

@@ Line 343: / Line 343: @@
 === Overall ===
-Text
+I think of all the areas that could have been improved upon, this is where I fell short.
 == End of File ==
 |}

← Older revision		Revision as of 04:33, 13 August 2021
Line 269:		Line 269:

	== Budget and Pricing Models ==		== Budget and Pricing Models ==
		+
		+	[[File:PiggyBank.jpg\|600px]]

	We'll be talking about the pricing models used by [[VisuStella MZ]].		We'll be talking about the pricing models used by [[VisuStella MZ]].

@@ Line 291: / Line 291: @@
 The next negative came in how we overstuffed the '''Wave'' bundles.
 With the calculations made [[Why does VisuStella MZ cost more than RPG Maker MZ|here]], we can see that each Wave reduced the potential earnings of its set of plugins by 60% to 70%.
-It would have been more lucrative to put only 6 plugins per Wave instead of 9.
+It would have been more lucrative to put only 6 plugins per Wave instead of 8 to 10.
 This would have made it easier for the team to maintain and produce, too.
 As such, this was a bad judgment call on my part.
@@ Line 301: / Line 301: @@
 Where the total amount of plugins it held was worth around the $500 range, we sold it at $100.
 Stuffing 8 '''Waves''' into it caused us to stay in the red even longer.
 === Challenges ===
-Text
+Keeping the budget above the red to pay team members to maintain and expand the library was a big challenge at the start.
 === Positives ===
@@ Line 320: / Line 335: @@
 And we still have over 100,000 downloads in total.
 This is pretty good for the first year.
 === Overall ===

@@ Line 301: / Line 301: @@
 Where the total amount of plugins it held was worth around the $500 range, we sold it at $100.
 Stuffing 8 '''Waves''' into it caused us to stay in the red even longer.
 === Challenges ===

@@ Line 268: / Line 268: @@
 Let them worry about it instead.
-== Pricing Models ==
+== Budget and Pricing Models ==
-Text
+We'll be talking about the pricing models used by [[VisuStella MZ]].
 === Negatives ===
-Text
+The beginning was a rocky start.
 === Challenges ===
@@ Line 282: / Line 295: @@
 === Positives ===
-Text
+While running the [https://www.patreon.com/Yanfly Patreon] for [[Yanfly Engine Plugins]], I often found myself overworked.
 === Overall ===
 Text
 == End of File ==
 |}

@@ Line 205: / Line 205: @@
 However, if I'm to be honest, obfuscation just so happens to be the low-hanging fruit that the drama-inciters are taking advantage of.
 Having done the research myself, the majority of the individuals using the obfuscation argument are those who were already speaking ill of team VisuStella to begin with.
-Those comments were made before the obfuscation of code was even discovered.
+There were already comments made by those individuals about [[VisuStella]] before the obfuscation of code was even discovered.
 As such, they were never the target audience to begin with as their sole interest was to promote FUD.
 But with that in mind, the high majority of [[VisuStella]] users say that the quality we bring out is well worth the obfuscation.

@@ Line 9: / Line 9: @@
 As the team director for the majority of the year, I'd like to take some time to reflect and review what went on during the year as far as developing and maintaining the library goes.
 There are negatives, there are challenges, but there are also a lot of positives.
 I'd like to take that time to talk about them so that the [[VisuStella MZ]] team can have a clearer understanding going forward.
 This article can also serve as insight to any potential plugin devs who plan on developing their own libraries.