In rot13: gung rkcynvaf jul V tbg pbashfrq nobhg gung qbhoyr-fynfu cvrpr’f tybj pbaqvgvba, naq vs lbh ybbx pybfryl gur gvgyr one npghnyyl qvcf n ovg jura gur j’f tybj pbaqvgvba vf zrg
3p0ch
Creator of
Recent community posts
Hints in rot13: Lbh pna gryy gung gur onzobb gung’f bar oybpx ybat zhfg fgevxr n fcrpvsvp rarzl orpnhfr vg pna’g or ebgngrq, naq vg pna bayl ernpu gur fnzr iregvpny yriry nf vgf gnetrg ng n fvatyr cbvag ba gur znc – lbh pna’g chfu vg gb gur fnzr iregvpny yriry vs vg’f gbb pybfr gb gur gnetrg orpnhfr gurer’f ab fcnpr gb chfu vg iregvpnyyl, naq vg jba’g uryc gb chfu vg gb gur fnzr iregvpny yriry vs vg’f gbb sne njnl orpnhfr gura lbh pna’g chfu vg sbejneq nsgrejneq.
Gura guvax nobhg jurer gur gjb oybpx ybat onzobb fubhyq or fvapr vg jvyy arrq gb fgbc gur iregvpny zbirzrag bs gur bar oybpx onzobb ng gur fcbg gung lbh vqragvsvrq. Vs gur gjb oybpx onzobb vf orybj gur bar oybpx onzobb jura vg fgbcf vgf zbirzrag, gura lbh’yy or va na vzcbffvoyr fvghngvba orpnhfr gur gjb oybpx onzobb jbhyq or fghpx naq pna’g or chfurq naljurer. Fb gur gjb oybpx onzobb zhfg or nobir gur bar oybpx onzobb jura lbh trg vg vagb fgevxvat cbfvgvba.
This is the most confounding one of the year for me too. I still haven't solved it, but managed to (rot13) trg n pbeare pyrnerq bhg. Znxr n W funcrq oybpx ntnvafg gur gbc jnyy, n fvatyr oybpx ntnvafg gur gbc jnyy gb vgf yrsg, naq gur ynfg oybpx 1 fgrc orybj gur hccre yrsg pbeare. Pyvzo vagb gur W naq chfu vg gb gur fvatyr oybpx naq gura onpx n fcnpr gb trg n fdhner bs terra pyrnerq, gura chfu gur fvatyr oybpx naq W gb gur yrsg jnyy. Lbh pna svantyr lbhe jnl gb trg gur pbeare pyrnerq bhg naq znxr n oybpx ernpu gur ybjre pbeare, ohg ner gura fghpx jvgu n oybpx va gur hccre pbeare.
It seems like that could be the start of a solution but IDK.
FWIW I tried "I'm too far gone" after I saw this, and I could solve ITFG, but this one still has me stumped.
I like the game so far and have suggestions:
I agree with requests to have a "make time go even faster than the fast button" button, and theorange4's comments about revamping the employee screen.
After I click the button to hire a new employee, I'd like to have the new hire's stats show up in a popup window or smth with "Keep or Axe" buttons since right now I have to click on them (after scrolling down a long list if I have a bunch of employees) and decide whether they're worthy. If you think it would help add a strategy element, maybe you could have a finite labor pool and if you Axe someone they're gone for good, so players can't just reject anyone with less than 20 stat points. With new potential hires gradually trickling in over time if you exhaust the labor pool.
I'd like to be able to ditch a project or a research track if it's becoming clear it will take forever, or the console gets discontinued, or just because I feel like it.
I also ran into the bug where if I go back to the main menu and then continue a game, time doesn't start until I go to a submenu (make a new game, research, or smth) and then come back to the top level gameplay screen.
In the plots of game sales on the top level screen, I'd like to see numbers for current monthly revenue and units sold (not just plots without y-axis scale indicators).
Also, in this game I made a gamejam game in 2 days with text-only graphics at lowest possible quality and no advertising and it was a multimillion dollar smash. I want to find the place this game world is based on.
Sounds like it should work, and if you think you might change the structure of your save files in the future and would rather just have to change the normal save files (for a desktop/console export) and not worry about also changing how PlayerPrefs saves the data then that approach might be less work in the long run. Just be sure to either ensure backward compatibility, or change the idbfs subdirectory if you do make any changes that break backward compatibility and you actually want to lose the old data.
On the other hand, if you don't think you'll need to mess with the code for save file structures, it might be easier to just pop in the class to override PlayerPrefs for HTML5 exports and be done with it.
In case you wanna use it, a while ago I came up with a way to make Unity not lose save data stored in PlayerPrefs when you update a web game. Source code is at https://3p0ch.newgrounds.com/news/post/1086279 You'll make everyone lose their data when you push an update implementing this for the first time, but then all future updates won't lose everyone's save data.
Getting a 3D game made in the course of a week-long jam, and one that actually makes use of 3D with multi story buildings, is quite a feat. It did its job well as an exploration game, and I'm not sure if the assets were already laid out in the town's structure or if you did the level design as part of the jam, but it was well suited for exploration. Having four actions and being told to apply one or a couple to each soldier as you find them felt like it didn't really add much, and it might have been fine to just find soldiers and press Space or something to automatically do whatever's necessary, but if you plan to expand the game post-jam I could certainly see minigames for each of the ways you need to help the soldiers being fun.
I followed the link and tried to run the game, and I got an error message at the top of the screen saying
Unable to parse Build/Builds.framework.js.br! This can happen if build compression was enabled but web server hosting the content was misconfigured to not serve the file with HTTP Response Header "Content-Encoding: br" present. Check browser Console and Devtools Network tab to debug.
I've always been a sucker for a good puzzle game, and this one doesn't disappoint. There were a couple of spots where I was wondering how in the world a level could even be possible until remembering that I could toss people around, or make use of another approach that I don't want to write without spoilers but which you can probably guess, and getting that "outside the box" feeling while staying within the rules that the game sets is always a good thing.
I ran into a bug where, after I realized it would be a good idea to use the watermellon's ability to force everyone to attack it for half damage and combine it with the flaming cherries(?) ability to inflict damage on anyone who attacks a particular target, the last of the enemies in the line died in the process of attacking the booby-trapped ally and it softlocked without letting me pick actions for the next turn. Aside from that it was an impressive game for a jam and I can't fault a corner-case like that considering that the game was made in a week.
When I encountered clues that were just a question mark, meaning I'd having to just run around and bump into people randomly after finding the contact with the known clue, that put a damper on things for me. But the fact that I kept playing that far into the game tells you how fun it is. For post-jam development, I think I agree with Anna that giving the player an "interact" action to find contacts with wrong guesses making you lose time (attracting the attention of assassins) would be a good way to cut down on random guessing tactics, but if you do make changes to penalize random guessing then you'll probably want to get rid of good guys with unknown actions.
It caught me a little off guard at first because I wasn't quite sure how Marry would react to different things, but after trying stuff out I could eventually get through and in retrospect the solutions seemed so clear that I'd smack my head for not seeing them sooner.
It also teaches a good life lesson: always keep a stash of lollipops in your basement, just in case.
After playing the game, and seeing comments about the camera moving too slow, I realized you got caught in dev hell where you need to keep everything from being too visible all at once in order to keep the last level from being trivial but by doing so you had people turned off by it. Damned if you do and damned if you don't; a situation I recognize :p. But the concept of spotting the fake based on kinetic parameters instead of static features is a good one that I haven't seen done before, so if you expand the game post-jam to meet your original vision without the franticness of trying to finish by an insane deadline then maybe there are ways to do it like having a cycle of actions with true aliens following the same cycle but starting at different positions within the cycle so there's less (or no) need to not show them all. And there are likely many more ways to do it, so plenty of fertile ground.
As someone who likes to do Sudoku puzzles from time to time, this really turned things on their head for me. I'm used to taking my time and spending a good 10 minutes or so solving a puzzle depending on the difficulty, but here all of that goes out the window and you've just got to frantically find the easiest solutions you can as quickly as you can... it's like Sudoku mashed with Warioware! It's a completely different experience than what I was expecting but I also like a good fast paced game so it definitely works. As others have said, the production value is clearly top notch especially considering the time constraints of a game jam.
The web version was a little off because not everything would fit on screen -- going fullscreen improved it but didn't completely get everything showing on either Chrome or Firefox. That aside, I agree with ChePhan about using the ghost to slash being easy to get used to; it's innovative in that I can't think of games that have used it before yet it does quickly start to feel like a very natural way of doing things.
Yep, I agree with the other reviewers that the difficulty with the insanely fast homing enemy was too much for me. I got the double jump and circled back to the starting area, then made my way into the zone that looked like organic foliage before having died so much that I had to ragequit. This game definitely looked like it would be good if I could make it farther. I admit my own game is also one where I expect players to die a lot, and you have a quick restart which is important in pulling off such a game. In mine I also nerfed the enemies a little bit each time the player dies so eventually it gets easy enough for them to win; I'm not sure if you would consider that a good design approach or something you would want to do in games where you know it's gunna be hard, but since I did it you can see it in action (admittedly in a different genre of game) and whether it "feels" allright.
The artwork was outstanding for a game made in a week, and it was a fun experience to play. I agree with Team Quest - I'd love to see it developed further with more puzzle mechanics and a backstory; I know that's beyond the scope of a Game Jam, but jams can be good for finding concepts like this that work well and could be expanded on.
It's a really creative idea to have pulled off for a game jam! The only thing I didn't like was encountering levels where you needed pixel-perfect positioning of the blocks when you switch in order to get it to work. If there's some way of making them push each other so they're not overlapping when you try to switch with a little overlap instead of just having the switch fail, and if you can give a little grace period when a jumping block hits a ceiling before gravity kicks in and it starts falling, then that should eliminate the need to be pixel-perfect at those points that I've come across so far.
This command worked in my gamepad mapper:
localStorage.setItem("gamepad_configuration", JSON.stringify(config_data));
The only thing that stands out is the capitalized 'Window'. If I go to the console and type "Window.localStorage" it shows undefined, if I type "window.localStorage" it shows a length zero object. If that's not the issue, it might be hard to debug without seeing the code.
Gamepad support in HTML5 games is currently pretty bad. Even if a framework or game engine says it supports them, in practice I've found it to be very unreliable especially when using different gamepads on different systems, primarily because the underlying JavaScript Gamepad API doesn't map buttons and sticks consistently. If there are reliable implementations out there, I haven't found them.
So I wrote a tool in JavaScript that you can launch from within your game that asks the player to press all the buttons and move all the sticks on their gamepad while it listens, stores that data in their browser's LocalStorage where games can read it, and then sends them back to your game. A nice aspect is that if the player configures their gamepad from ANY game on the site, EVERY game on the site can read the data and use it for gamepad support without them needing to run the tool again.
The Gamepad mapper page is linked here, and you can see how I used it in practice in my game Quad. The Gamepad mapper's page has links to demos showing the gamepad mapper being used in Unity, Godot, HaxeFlixel, and pure JavaScript including instructions and source code for those implementations in the author comments.
The picture of the guy being dragged by the ball when he throws it hard amuses me more than I'd like to admit. Throwing it felt a little clunky to me too, and specifically it seems due to a mismatch between how full the bar is and how far the ball actually gets thrown -- about half strength seems to make it go just as far as full strength, so maybe just rescaling it so it matches the distance would make it feel better? (Unless it's not a bug and its a feature of making the distance traveled fall sharply if the inmate starts getting dragged.)
The graphics and fundamentals of gameplay were nice, but it feels like it needs to demand strategy or skill from the player. I could walk right over the enemies with impunity and just gather resources and build up defenses day and night, and after maxing the defenses all that's left to do is watch. With a little bit of either danger from the enemies and/or requirement to build and rebuild strategically to fight them off I think it would be a pretty fun game.
If the game is losing web-based saves when you publish updates and you're using PlayerPrefs to store the save data, I came up with a solution to make it not lose data on updates. If you implement it in the next update then that update will still cause save data loss, but then it won't happen any more for any future updates. Feel free to use it, the source code and explanation of the underlying problem is here.