HiddenChest RGSS Player Executable

[kyonides]

"First There Was a Penguin And Then a Few Windows Suddenly Showed Up" the BUMP Stated Out of the Blue

Yeah, I have updated HiddenChest's version of friendly object oriented programming language, Ruby! First I had released the binary executable for Kubuntu OS and now there are the ones for Windows family of OS's. As far as I know, it runs on Windows 8.1 and 10, but I can't tell if it would do the same on Windows XP...  

@KDC
Well, since it's just a player executable, meaning you only will use it as a replacement for Game.exe, you only need to unzip the executable file and its dll's right where the Game.exe file itself is located.

If you've got a 64 bit Windows OS, then you'd need to download:

• hiddenchestwin64_ruby262_window or hiddenchestwin64_ruby262_console ZIP file
  
• x64-msvcrt-ruby262.zip
  
• dll64full.zip
  
• MapCustomResFixesXP or MapCustomResFixesVX RGSS1/2 script, it doesn't seem to be necessary for ACE

Then just extract them in your game folder's root directory, i.e. C:/KDC/Memorie in case that's where you've placed the Game.exe file.

[KDC]

@KDC
Well, since it's just a player executable, meaning you only will use it as a replacement for Game.exe, you only need to unzip the executable file and its dll's right where the Game.exe file itself is located.

If you've got a 64 bit Windows OS, then you'd need to download:

• hiddenchestwin64_ruby262_window or hiddenchestwin64_ruby262_console ZIP file
  
• x64-msvcrt-ruby262.zip
  
• dll64full.zip
  
• MapCustomResFixesXP or MapCustomResFixesVX RGSS1/2 script, it doesn't seem to be necessary for ACE
  

Then just extract them in your game folder's root directory, i.e. C:/KDC/Memorie in case that's where you've placed the Game.exe file.

Ah. I see. I'll do that and see if that works.

[KDC]

Did all of the above and.... it just closes for some reason. 

[kyonides]

Well, I would need to get more information on it before I can tell you what could be going wrong there. Actually, I gotta to tell you all that the script should be inserted above the Main script in XP or VX, he, he.

[KDC]

Well, I would need to get more information on it before I can tell you what could be going wrong there. Actually, I gotta to tell you all that the script should be inserted above the Main script in XP or VX, he, he.

I did do that before trying it out. But in short... I put the .dlls and .exes in the root of a copy of the project, for trying out purposes, where Game.exe would be located, double clicked one of the hiddenchest_####. The window popped up, like normal, but after a bit it didn't even go into the Title Screen. It just closed.

[kyonides]

Mmm, well, it could be due to the inclusion of some old Ruby DLL file in the dllXXfull ZIP file... He, he It seems I just forgot to get rid of it before telling people to decompress them after placing the current Ruby DLL there. Just place the newest version of the DLL there once again and it should find it, thus letting you play it as usual. If that's not what's happening there, I'd need to come up with some method to retrieve a log file.

Usually the log would be created by replacing or commenting out...

Code:

rescue Errno::ENOENT
  # Supplement Errno::ENOENT exception
  # If unable to open file, display message and end
  filename = $!.message.sub("No such file or directory - ", "")
  print("Unable to find file #{filename}.")
end

with...

Code:

rescue
  File.open("log.txt", "w") do |file|
    file.puts $!.message
    file.puts $!.backtrace
    print $!.message
  end
end

Meanwhile I will reupload the dll64full ZIP to prevent people from ending up in the same strange situation as you did not long ago.

Edit

OR just place the dlls found in the dllxxfull ZIP file not in the dll or dll64 directory but the game's root directory.

Side Note
Due to previous incompatibilities with side by side configuration, the latest versions of HiddenChest for Windows do not support loading DLL's found in a custom directory placed in the game's root directory.

[KDC]

Mmm, well, it could be due to the inclusion of some old Ruby DLL file in the dllXXfull ZIP file... He, he It seems I just forgot to get rid of it before telling people to decompress them after placing the current Ruby DLL there. Just place the newest version of the DLL there once again and it should find it, thus letting you play it as usual. If that's not what's happening there, I'd need to come up with some method to retrieve a log file.

Usually the log would be created by replacing or commenting out...

Code:

rescue Errno::ENOENT
  # Supplement Errno::ENOENT exception
  # If unable to open file, display message and end
  filename = $!.message.sub("No such file or directory - ", "")
  print("Unable to find file #{filename}.")
end

with...

Code:

rescue
  File.open("log.txt", "w") do |file|
    file.puts $!.message
    file.puts $!.backtrace
    print $!.message
  end
end

Meanwhile I will reupload the dll64full ZIP to prevent people from ending up in the same strange situation as you did not long ago.

Edit

OR just place the dlls found in the dllxxfull ZIP file not in the dll or dll64 directory but the game's root directory.

Side Note
Due to previous incompatibilities with side by side configuration, the latest versions of HiddenChest for Windows do not support loading DLL's found in a custom directory placed in the game's root directory.

Surprisingly, all the dll files were in the root folder.

[kyonides]

Huh? O_o? Then I would need you to send me the log.txt file to read the error message and backtrace info found there. Are you testing it on a blank project? Or is it an old demo you haven't touched in a long time? Are you trying to play any XP or VX or VX Ace game, KDC?

[KDC]

Can't find the log.txt file T.T I tried it with a basic copy of a project I'm working on with XP.. to be on a safe side of things in case things went wrong.... and a copy of a VX Project.... and just a completly initial one from RPGXP recently.

[kyonides]

OK, if you plan to use it to playtest VX or VX Ace's game, you'd need to fetch the hiddenchest.conf file because it will quickly tell the executable you need to grab RGSS 2 or 3 instead of the default option, RGSS 1.

In order to get the log file, you'll need to copy and paste the code I mentioned above in the Main script by replacing that part of the original code. Did you do that already? O_o? Which version of windows are you using now? XP, Vista, 7, 8, 10?

I've been wondering if there's a missing file. Whenever that happens, you wouldn't get an error message or pop up window.