itch.io

The issue should be fixed now.

Thanks for the report. I was able to reproduce the bug. I have an idea what may be causing it, but I'm not sure it will be easy to fix. I may try to address it someday, but it's not a priority for an immediate fix. While annoying, this bug is easy to work around. I've added a warning to the game's description. The game is also available here and here, and these versions are not affected by this bug (AFAIK).

The web version uses standard keyboard controls. The issue appears to be on your end; one possible reason is that you might be using an extension that blocks keyboard input. Please try a different browser. Note that on Firefox, even gamepad input should be working.

Нет редактора. Вообще. Не только на Android.

На устройствах с тачем, читы включаются нажатием на невидимую кнопку в верхней средней части экрана . Скорее всего это и произошло . 

Ещё на клавиатуре (если она вдруг подключена), F8 включает читы . Если нет клавиатуры, но есть геймпад , в теории может быть , что какая-то кнопка на нём срабатывает как   F8, можно попробовать перенастроить его.

Информация по читам.  Других неочевидных кнопок или сочетаний нет .

Thanks for the report.

There's still one thing I would love to see improved, dunno if that's possible or you want to improve it at all: control scheme settings.

Gamepad button names aren't consistent across different devices and OSes, so this feature won't work most of the time and will do more harm than good for most devices. In fact, a similar feature was previously implemented for Xbox controllers but worked poorly, so I removed it. It is possible to rename buttons manually, but only on desktop platforms. 

Pause screen how deep you are (in feet), it seems that is missing from the translation?

"FEET" is definitely in text.json (the translation file), and all other strings in the pause menu are translated for other languages. Maybe you assumed this text was from the level editor and didn’t translate it?

Same with the $ in the result screen, this is still the $ instead of the € sign.

I'll investigate - the fix should be straightforward.

Anyway, these issues are minor enough that I'll wait to include fixes for them in a future update with more significant changes, since building and releasing takes substantial time.

Read the instructions. This topic is for general questions about the translation process. If you started translation, create a new topic for it.

Ouch! Wishing you a quick recovery!  

Actually, the game probably doesn't require much testing since there are no major changes, so I'll likely release it once I polish the last few things.

The latest build now on GitHub: https://github.com/yancharkin/SpelunkyClassicHD/releases/tag/1.2.1-rc

Thanks for the update!

Are you sure you're running the latest version? The dollar sign should be replaceable - unless you're referring to the animated sprite in the last screenshot, which isn't (yet). I might fix that later.

Is your controller working now?

Here's the latest build. Would be awesome if you could give it a quick test.

No problem at all! I've actually been quite busy myself lately and haven't had time to focus on the project either. Please take your time - there's no rush on this. Besides, I'm not sure I'll have much time for the project in the near future.

Have you had a chance to test the latest version?

Thanks for the report. This bug was fixed in the latest beta: https://github.com/yancharkin/SpelunkyClassicHD/releases/tag/1.2.1-beta2

Builds with the gamepad configuration reverted to the previous working state are now uploaded to the GitHub release page.

Was the last version where your gamepad worked the previous beta or version 1.2.0? There have been some changes since 1.2.0 that I haven’t tested on Windows, so they might have introduced issues. I can revert them if needed.
Also, have you tried connecting the gamepad before launching the game? That should work. It works fine for me - just tested it on Windows with a cheap no-name gamepad.
Good luck with your work - this project can obviously wait.

Ah, yeah, I was using the first version of the translation.
I've uploaded a build with the latest changes to the GitHub release page.

The following lines are still too long:
[55] RAKETENRUCKSACK UMGESCHNALLT! ACHTE AUF DEN RÜCKSTOSS!
[62] MACHETE BEKOMMEN! JETZT HABEN NICHT NUR BÜSCHE VOR DIR ANGST.
[60] STAMPFSTIEFEL ANGEZOGEN! 1 PAAR STABILE STIEFEL SCHADET NIE!
[57] SCHWUNGSCHUHE ANGEZOGEN! NOCH NIE WAR SPRINGEN LEICHTER!
[67] DAS AUGE VON UDJAT ERHALTEN! ALTE ÄGYPTISCHE KRÄFTE SIND ZU SPÜREN.
[64] ICH KANN DAS ZISCHEN VON SCHLANGEN HÖREN... ICH HASSE SCHLANGEN!
[55] ZUM HOCHWERFEN OBEN UND ZUM FALLENLASSEN UNTEN DRÜCKEN.
[64] ALS ICH MIR DIE LETZTEN WORTE MEINES VATERS INS GEDÄCHTNIS RIEF,

P.S. Also, with the language quick-switch feature working better now, it's easier to test translation.

The game’s now 64-bit, thanks to the update to the latest GameMaker version.

Beta build is published! You can try it out now. I believe all your suggestions have been implemented - thanks again for your contribution, it’s truly appreciated!

https://github.com/yancharkin/SpelunkyClassicHD/releases/tag/1.2.1-beta

Regarding your translation:

• For the contributors list: your nickname is MasterPhW, but could you also provide your email?
• The files sNewButton.png and sNewButtonPressed.png are from the editor, so there’s no need to translate those.
• A few new strings have been added, and at least one wasn’t translated: "YOU FEEL BOUNCY."

• Some strings in your translation are too long. Ideally, each string should be no more than 40 characters to fit on a 4:3 screen, or 53 characters for 16:9. That includes letters, spaces, and punctuation. I know it’s not always easy, but try to get creative! It’s even better to have a grammatically imperfect phrase than one that gets cut off and becomes unreadable. If possible, please shorten the longer strings.

You can report any issues you find in the 1.2.1 beta release here.

Quick update: all issues are fixed (I think) and a few improvements have been made. While I’m at it, I decided to clean up the code a bit - which might accidentally break somethings -  so I’ll release a beta build in a couple of days.

Thanks!

I'll be a bit busy over the next few days, and implementing everything will take a couple more, so I’ll get back to you in about a week (maybe a little sooner).

Yeah, adding contributors to the credits is probably a good idea. What info would you like to include about yourself?

- It's a bit different from the textures that can already be replaced, but yes, it’s possible. If you translate them, I’ll implement this feature.

- These strings have different formatting, allowing adjustments by adding or removing spaces (see the picture for an example of what's correct vs. incorrect). The game was never designed for translation, and positions were hardcoded for English. It could be implemented better, but fixing it would likely take more time than I’m willing to invest for such a minor improvement.

- Either way is fine.

- I don’t think you need to use the script to create the charset for German. Just modify the English charset - most additional characters are fairly easy to create (except maybe ß). If the resulting font is larger than 16x16, create a font.json file (see the Spanish example). charset_small.png is required, but it’s just a scaled-down version of charset.png (yes, it’s strange, and could likely be done better, but again, it’s not worth the time).

- It allows for quick switching to that language using a shortcut ("L" by default) or a touch button. I think it could be a semi-useful feature for those learning a foreign language, it works pretty well in the tutorial  (not as much later on -something that could be improved).

- Yes, they can be safely removed. I’m not planning to re-add the editor. That’s just a leftover from when I wasn’t sure if it would be needed.

Ok, feel free to ask questions I'll answer them ASAP.

First of all, I’d like to clarify one thing about this project, as it will answer many "why" questions.

Originally, I just wanted to build a Linux version to see if it would work - nothing more. If I had bigger plans, I would have done things very differently. But now, it is what it is, and many things are implemented in a less-than-optimal way (and mostly not by me, but by the original creator and those who worked on the port my version is based on).

Some things are easy to improve - I simply missed them (and no one reported them). Others, however, would be unreasonable to "fix" at this stage, as doing so could cause more harm than good and would take too much time.

This bug was expected - something changed in the latest GM runtime, but I think I know how to fix it. On the other hand, in fix1 (which was built with a much older runtime), the jump touch button doesn’t work correctly, and I don’t know how to fix it. So, the choice is obvious now. Thanks for testing!

Regarding translation, it would be great if you could do it!

Instructions can be found here.

If you have any questions, you can ask here.

Or you can create a new topic like these:
Spanish Translation
Ukrainian Translation

Yes, please do a quick test of fix2. I just need to know if it works at all — further actions depend on it.

Maybe the GM Runtime or Android SDK used for this build isn’t playing well with your device. Try these builds — you’ll likely encounter some bugs, but there’s a chance they’ll at least launch:

https://mega.nz/folder/rlZjwDRB#yPbGbQ6A66D_D3lxgUqb7w

If you’re willing to help fix this issue, please create a new GitHub issue and include info about your device and OS version.

If none of the builds work, and if possible, please provide the output of this command after launching the game:

adb -s <your_device> logcat

No guarantees, but I’ll try to do something.

- Which version have you installed? More variants available here: https://github.com/yancharkin/SpelunkyClassicHD/releases/tag/1.2.0 Try yyc build.

- Have you tried the HTML5 version (it was available among the old builds)?

- Is there any kind of error message? If there isn’t one, the only way to get useful info is to connect your device to a computer and run ADB. Can you do that?