Commercial System Package

[DerVVulfman]

COMMERCIAL SYSTEM PACKAGE
Version: 1.2

Introduction
For over a decade, the number of Independent Game Developers has increased. And while there are many packages at the disposal for one to create their wares, producers and distributors of Indie Games have chosen to put requirements upon those wishing to enter the commercial field:

1. A splash page before game start
   
2. An options page to control game volume
   
3. Game start in Full-Screen Mode
   
4. Credits for all in game development

Designed for RPGMaker XP, this package wishes to sate the desires of software distributors by providing much of the bare-bone features they require. It may not include all features and may not have graphics up to one's personal standard, but it should be a starting point for those wishing to enter the commercial market. And this package contains software by various individuals, rather than from a single scripter. As such, please note and give full credit to these individuals. A credits display is one of the requirements after all.



Features

• A repaired command_355 script (at no charge)
  
• Disabling F1 and the Alt+Enter Full-Screen toggle keys
  
• Preventing game freeze if another 'window' is in focus
  
• Creation of an actual game configuration file - Full-Screen game mode as a default setting
  
• Creation of an actual game data folder to store save-game and configuration data
  
• Volume control for both music and sound effects, including battle animation audio
  
• More direct control over full-screen and windowed-screen modes
  
• Display of one or more splash screens, each with their own duration and audio effects
  
• An editable Title Menu Options feature written straight into the field map itself

Demo
Here's the package!



Introduction
See the help (.Chm) file for instructions.



Compatibility
Designed solely for RPGMaker XP. It may conflict with other scripts based on script placement.



Credits and Thanks
A package meant to satisfy the needs of game distributors requires many talented people. But who are these individuals, what did they create, and what does their work accomplish? It is here where you get to learn what software was used to develop this package and what individuals wrote the software in question.

• DerVVulfman
  
• Thomas Emebo
  
• KK20 (Boisterous Hero in Save-Point)
  
• Jaiden
  
• Chainsawkitten
  
• PK8
  
• Pelip
  
• Kyonides-Arkanthes

Terms of Use
Based on the apparent terms for all listed scripters, free for use. See the help file for more.

[Pelip]

Hey umh, I used your script/s in a my fangame, everything is fine to me but when i released it, "custom modules" gave an error to almost everyone who downloaded it on the line 193, I see it's a line when the game tries to reach the Documents folder, so I thought it was an access problem/the computer won't let access the game to that system folder and then it gave that error. But I dunno actually, I told them to make a folder in Documents/My Games/ for maybe don't make the game do it, but it didn't fixed it, I also tried to make them to run the game as an administrator, but nothing. Then I gave up, and here I am..

The demo of my fangame is on this page: https://gamejolt.com/games/deltataleofficial/428285

The error is this: https://i.gjcdn.net/data/comments/55/226...pqvkf6.png

[DerVVulfman]

That is a rather 'strange' error. It is saying that it cannot find the Application Data folder using a very common routine. And since it is having difficulty attempting to look for the application data folder, it found no MyGames folder... And this code certainly works on 32&64 bit windows systems, both 7 and 8. (I have a 32bit Win7 lappy and 64bit Win 8.1 desltop).

Doing a search, it appears that this isn't the only package that has issues with the AV_APPDATA value, mostly all with Windows10 systems. I am currently working on a revision to take care of the issue involving (1) using a method to re-acquire the application data folder for Windows 10 users based on just-learned criteria and (2) handling issues if no valid data is acquires (ie Nil), which would force the saves to use the root folder.

You won't have to do any real update except to the one 'script' method if all goes right.

[Pelip]

That is a rather 'strange' error.  It is saying that it cannot find the Application Data folder using a very common routine.  And since it is having difficulty attempting to look for the application data folder, it found no MyGames folder...  And this code certainly works on 32&64 bit windows systems, both 7 and 8.  (I have a 32bit Win7 lappy and 64bit Win 8.1 desltop).

Doing a search, it appears that this isn't the only package that has issues with the AV_APPDATA value, mostly all with Windows10 systems.  I am currently working on a revision to take care of the issue involving (1) using a method to re-acquire the application data folder for Windows 10 users based on just-learned criteria and (2) handling issues if no valid data is acquires (ie Nil), which would force the saves to use the root folder.

You won't have to do any real update except to the one 'script' method if all goes right.

Alright then, I have both win 8 and 7 too and in both worked, tho not having win 10 I couldn't tell if it worked on it too.

[DerVVulfman]

TIME FOR A BUMP!

Ladies and gentlemen, I received information from Pelip that the UserPath module within the package did not function on some PCs.

Given the error, it appeared that their systems did not contain a registry entry for the Application Path that has been common from Windows XP through to Windows 8.1. And on doing a search online, it appears that my system wasn't alone in this. The issue appears to be a Windows 10 issue.

As such, research was made to identify the newer registry path and entry which would be acceptable to Windows 10 users, a path that likewise does appear within the Windows 8.1 registry. This new path has been added to the UserPath system.

This does not mean the older Registry path was removed. On the contrary, that would ignore the usefulness of the older Registry path for PCs using earlier versions of Windows. Both systems work in tandem. As such, if one path was not detected, UserPath would look for the second in its place.

In the unexpected event that neither these nor the documents folder locations are detected, measures have been put into place to avoid errors. However, this would mean that it may fall back upon the root folder holding both game saves as well as the configuration file. Still, this should be considered a rarity.

And because of the detection, Pelip (or Andrea87Sky of RPGMakerWeb.com) is now in the credits as a betatester for my UserPath system.

[Pelip]

TIME FOR A BUMP!

Ladies and gentlemen, I received information from Pelip that the UserPath module within the package did not function on some PCs.

Given the error, it appeared that their systems did not contain a registry entry for the Application Path that has been common from Windows XP through to Windows 8.1.  And on doing a search online, it appears that my system wasn't alone in this.  The issue appears to be a Windows 10 issue.

As such, research was made to identify the newer registry path and entry which would be acceptable to Windows 10 users, a path that likewise does appear within the Windows 8.1 registry. This new path has been added to the UserPath system.

This does not mean the older Registry path was removed. On the contrary, that would ignore the usefulness of the older Registry path for PCs using earlier versions of Windows.  Both systems work in tandem. As such, if one path was not detected, UserPath would look for the second in its place.

In the unexpected event that neither these nor the documents folder locations are detected, measures have been put into place to avoid errors. However, this would mean that it may fall back upon the root folder holding both game saves as well as the configuration file. Still, this should be considered a rarity.

And because of the detection, Pelip (or Andrea87Sky of RPGMakerWeb.com) is now in the credits as a betatester for my UserPath system.

Oh alright thanks, glad to help someone ^w^

By the way that means that the script is now fixed or not yet?

[DerVVulfman]

Fixed. And only the 'UserPath' module needed edits.

Well, that and having to rewrite the help file to change the version number and add your name into the UserPath credits.

[Pelip]

Alright it now works, but seems there's another problem in windows 10 with loading the F1AltEnterF12 DLL.

Basically this guy had a problem on loading the F1AltEnterF12 DLL, I asked they what was their computer and he said "a samsung with an huge screen" also he told me it was win 10, i'm not sure if they was just some guy creating false problems, but it's better if i report this problem too.

I also asked him if their's download was corrupted or the DLLs folder was missing, but they had it anyway and they tried to download my demo again, but it didn't fixed it.

The problem is this: https://www.dropbox.com/s/03erd18w2pecu5j/1.PNG?dl=0

[kyonides]

Just in case I would ask you if that DLL is Windows 10 compliant. Some dlls might work on several Windows releases and break when the next comes out. It's curious to see a LoadLibrary error that's not rubygem related. I know, we're talking here about a DLL written in C or C++ and being called through Win32API (miniFFI under the hood).

There seems to be another way to deal with the F12's reign of terror:

Thread.new(system('Game.exe'))

And probably some variable to keep track of this need for a separate thread.

[DerVVulfman]

Given that Pelip's users have been Windows10 users and had no further issues, and that the creator of that dll is a Windows10 users, I think there should be no problem.

The concept of Thread.new(system('Game.exe')) is something you can investigate and run tests upon. It would be entertaining to hear about your endeavors in that within the "whats up RMers" topic.