Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

notsam22

9
Posts
A member registered Jan 06, 2024

Recent community posts

Very cool game, though the tiles will sometimes go completely white, preventing any digging (as I assume they have reached NaN and are interpreted by the game as having infinite depth).
This can happen at any tile at seemingly any point of the game, likely due to tiles updating very quickly. 
Also tiles will sometimes just... undig themselves over time? Had a tile at ~180 for a few minutes, then I dug it again and it went to like 147. Very strange.
[SPOILERS BEYOND THIS POINT]



Also the scaling gets really wack. ESPECIALLY via the gardens. Can go from like 10k ft tiles to millions extremely quickly via the worm and gopher efficiency boost. Pairs very well with the Denisovan Bracelet permanent upgrade which got me like +10,000,000,000% research for every artifact. You probably want to give reachable hard caps to the one of a kind items so that people who buy them early aren't literally a billion times slower at getting research than I was. Also maybe make the other place a bit more useful, right now the only use is for discovering the bracelet (it's so forgettable I can't even remember its name).
8/10 game, my comment is only mainly issues so that they are brought to light.

I will just remake the instructions (tested on Brave and Chrome. Cannot confirm if it works on others):

Step 1: Open Developer Tools on the page of the game. This should be able to be done with Shift + Ctrl + i    ,  or with right clicking and selecting Inspect.

Step 2: Around the bottom of the tools should be a tab called Search. If it is not there, then find a button with the 3 dots and try to find 'Search' there.

Step 3: Search "vue". Make sure you pressed ENTER after typing it. In the results there should be one on line 175 that includes "https://unpkg.com/vue@next" . Click on it and it should take you to the line in the sources tab.

Step 4: First, make sure to create a new folder on your computer. Right click on line 175's text and select Override Contents. For Google, a little information thing may pop up, just click the 'Select Folder' button and select your new folder. A website warning may pop up with 'allow' and 'deny', allow the reading and writing to the folder. If this works, move on to step 5 and ignore the alternate solution listed below.
Alternative solution for Brave, (or perhaps any website if you've overridden stuff but deleted or modified the folder its trying to save to), it may not pop up and instead it will just act like it's overriding to stuff (a warning symbol will appear if attempting to save since it is saving nowhere). If that happens, there should be a little tab on the left side of the developer tools that includes a "Page" tab. Select the two right pointing symbols (>>) and select overrides. Then in this overrides tab, make sure 'Enable Local Overrides' is checked, [if needed, then clear the configuration via the circle with a slash in the middle symbol (Ø)] and press 'Select folder for overrides'. Select the folder you've made. A website warning may pop up with 'allow' and 'deny', allow the reading and writing to the folder. If there may still be issues, attempt to right click and select 'Override Contents' again.

Step 5: In line 175, remove '   @next   '  . The quotations should now read "https://unpkg.com/vue"

Step 6: Save with Ctrl + S. This should remove any asterisks (*) from the script name that indicate that the file has not saved.

Step 7: Reload the page (Ctrl + R while focused on it, or just hitting the reload button).

Extra notes: If you ever modify or delete any of the files or folders containing Override Content information, your browser may still think that it should write to whatever you had selected last. This can be helpful if you want to swap between modified and more normal overrides, but in general it can just end up with the game breaking again, so try not to mess with the folders or files.
If this does not work on Brave or Chrome, I assume it is not an issue with the steps. The last guide did in fact show an error for the bad line, but now for some reason it does not. I am not active on this account, so my response will likely be extremely late if I ever do respond.
As of writing, I am unaware if there are any issues that pop up while playing the game. I have only tested that all of the mess gets fixed.
Sorry for the very late reply.

I kind of just walked to the right of each stair room and got to the top at a high level, is that intended?

Woohoo! I did it! Wasn't as tough as I thought it would be, but it sure was tedious. Very good game.

My bad for the confusing instructions; here is a rewritten step 3:

Right click the problematic line (or really anywhere on the sources page). Click "Override content". It should ask you what folder you want to save it to, so create a folder on your desktop, then select that folder. If you did it right, you should now be able to edit the contents and follow step 4. Also, the little sidebar to the left of the sources content should show the page you are in as what seems to be a piece of paper with a purple dot at the bottom right

If step 4 is confusing;  removing "@next" should be possible by double clicking where the text is, which should let you start modifying the text. Then you can remove "@next".

If step 5 is confusing; CTRL + S should work to save the index. I do not know where a save button may be besides this shortcut.

Hopefully this clears things up.

As of recent, it seems like persistent cards will practically destroy the visuals with cloning and such.

(2 edits)

My bad, the ENTIRETY of "index.html" doesn't even pop up until you hit reload frame (reference the last step for directions). I have no idea why, but you can just reload frame then the error pops up only then. I got this working on Brave.

(1 edit)

Nice, and I found out how to fix up the game on the website itself.

1: Right click the game and find the button saying "Reload frame"

2: Go to the error trying to reference "vue@next" (line should say "<script src=...vue@next></script>") [website name not mentioned just incase]

3: Select "@next" and override the contents. Create a folder anywhere you want, and save that override to the folder

4: "index.html" should have opened with a purple dot, so go ahead and remove "@next" from the script

5: Save the index.html since it wont try reading it until it's saved, I think.

6: If it hasn't fixed yet, yet again right click the game and click "Reload frame"

Should be fixed for the website version, and the developers, if they ever fix this real quick, can have it patched in like 30 seconds. If this order doesn't work, then I probably didn't say something right due to me managing to struggle on finding a solution for a while.

P.S. "Incremental Game Jam Game" will read this save properly even with the fix.

Bummer. I assume that Vue dropped support from whatever this is formatted in (so this is probably V1 or V2), so this is practically doomed I guess.