Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

GreatCorn

15
Posts
43
Followers
A member registered Sep 02, 2020 · View creator page →

Creator of

Recent community posts

I'm pretty sure there's a lot of games that do it this way out there. The registry is fully capable and it just boils down to personal choice and accessibility considerations.

You can either search 'regedit' in the start menu or press Win+R, type 'regedit' and hit OK.

If you're not familiar with the Windows Registry and are planning to change some variables in it, I'd advise to be careful, a lot of important system stuff is stored in there.

A temporary (in-layer) save is erased when the player dies. The save data is stored in the registry at HKEY_CURRENT_USER\SOFTWARE\GreatCorn\MASMZE-3D.

I tried to fix it in the latest hotfix version (1.1_hf2), you could try if it works for you. There is also an option to turn off mouse smoothing in the options.

This issue is still non-replicable on any of the devices I tested with, so I'm blindly guessing what is causing it.  Sorry for the inconvenience.

Thank you for the comment! Glad you enjoyed it, thanks for testing on Wine! I did try it on an Android fork of it, Winlator. It ran pretty much perfectly, except for occasional arbitrary freezes, but it's Android, so I guess that's to be expected.

The ceiling tentacles can be evaded by crouching :)

Thank you for the comment, terribly sorry for the issue. Are those jolts accompanied by lag, freezes, or happening independently? I'll see what I can do to fix it.

Thank you for your comment, I'm very sorry to hear that. It would be of great help if you let me know what OS/compatibility layer/input setup you're using. 

For some reason, I was sure Windows would send WM_PAINT messages at monitor refresh rate, but apparently, that's not the case. I'll try rewriting the rendering loop and testing on more diverse machines.

Thank you very much for playing and for your comment!

I'll probably post a bugfix version and a source port once I finally do enough testing, but that would probably be the last update to the game.

The entities have their names, but they're not really 'officialized', because they're only present in code comments and as data labels. The game is too small for any kind of wiki, however, I plan on doing more stuff relating to the world/universe it is set in.

Thank you so much for trying the "game" out and for the very kind words!! This was planned as a sort of (tech)demo at the start, but it's likely that I'll be adding more content and updating the game later.

Very sorry about that. Even though Chromebooks are known for their performance issues, the game is still very resource-demanding and even more so because it is written on JavaScript. I'm working on updates and trying to come up with as many performance optimizations as I can. Your internet is only required to load the resources at startup, after that the performance does not rely on it.

Thank you for your comment! I understand the game may be unpolished in some places, I'll do my best to fix any bugs. As for the interaction - I'm trying to keep the feel and atmosphere as ethereal and vague as possible, but I guess I'll figure something out to make the game tell the player what they have to do and how they have to do it. The cassette tape is not necessary to complete the game, but it's never really told there that it isn't. Again, thank you for your attention and your time.

Thank you for your comment and the video, that was pretty quick! The game did emerge from the backrooms in a way,  as I was testing out THREE.js and wanted to make a 3D horror game in it. Off the top of my head were the backrooms, but I also wanted to make a demo for my other game. As I thought blatant copy-pasting was too boring, I decided to do something different.

Thank you very much for notifying me!