This seems to be a bug introduced *somewhere* in wine 6.x; 5.22 runs the game without issue.
Recent community posts
Weirdly enough I'm getting an unhandled page fault on read access to 0x24 at address 0x69885BD5 (and consistently so, the only variable is the thread ID) when running it under wine. Removing dxvk from the equation didn't change anything either.
If anyone gets version 4 to run under Linux (or some other version I'd have access to), please do let me know, since from what I've seen so far this does seem pretty nice & I'd like to at least be able to give it a proper try beyond a few seconds into it (it crashes a few seconds after clicking "Begin Story" / after the last card in the first round was played; whichever happens first).
I'm using Arch with i3 for windowing, which means it's using X11 and scales the applications directly after they are opened if it can (due to i3 being a tiling window manager).
Also, it's all good! It *is* a game jam entry, and if bugs like these weren't something to be expected; and this one really isn't game breaking either.
Yeah, the zooming and such seems to be a problem in general, and that one part of the dialogue is moved weirdly for everyone. I have not found the reason for that, but I also haven't really investigated why that happens yet.
I should probably have said so in my comment before, but yeah: I did find the option in the menu, but it didn't do anything - the other option that was supposed to change the menu style also didn't do anything by the way.
My main feedback would honestly be that the music is very loud, and I wasn't able to turn it off (though that might be a wine issue instead of an issue in the actual game; but I don't think that's very likely).
That said, it's definitely a fun idea!
This game was absolutely great! If there's any feedback I could give it'd be making the movement of the orbs a bit slower & maybe even stopping the timer when moving them; and apart from that just cleaning up the already very charming visuals a bit.
having played a few other Unity based submissions, it appears to maybe be an issue with either the newest wine (the thing with which you can run windows programs on Linux/Mac/BSD/etc) or the newest Unity versions; since it happened with a few of the other ones as well.
Anyway, if there's anything I can do to help investigate / fix the issue let me know ^^
This seems like a really fun concept!
However to anyone under Linux, esp. with more than one monitor, it will probably not work. Whenever my mouse exited the window, I couldn't look around anymore.
I really want to like this, but - be it bad luck or just me being impatient - some of the battles can just take *way* too long, due to both the player & enemy healing constantly.
That said, I really do like that you can *kind of* control where you're going on your wheel, that does give it some extra flavour beyond customizing your wheel that I really liked :)
I have yet to figure out what causes that part of the text to be moved to the top right weirdly; but I also haven't investigated it that much yet. I assume it has to do with spaces somewhere that shouldn't be there or something like that; but I honestly don't know.
Sometimes game jams are just a bug creation marathon XD
Oh, I really like that idea! I personally thought of linking more different statistics originally, like constraining an enemy to a certain height based on for example your health, something like that.
As for the bug, it's a known one and is fixed already in the fixed version of the game I linked in the description, that was caused due to the game over screen referencing the wrong background (two levels always share the same background, so the background ID is half of the level ID rounded down; and the game over screen tried the level ID directly); which you can actively see when dying to the mad scientist (level 2).
The mechanics could've definitely been explained better, but almost all of the dialogue was written in the last 10min of the game jam; otherwise it would've contained a few more tips along the way.
For example, instead of just "gliding" to a halt, a better strategy is to actively try to walk in the opposite direction; this brings you to a stop quicker and leaves less time in which you're vulnerable because of standing still; when someone is linked with your speed.
Fun fact, I actually *did* search for wasm-compatible audio for bevy, and the library I found *is* compiled in. It's just that we didn't have any time to actually add any sound because of the deadline; hell (ignoring the grace period I didn't know about until literally a few seconds before it ended), the game isn't even playable after the half-way point because of game breaking bugs that I just didn't catch because I couldn't really test much.
Maybe we'll actually continue updating this game a bit; we'll see.
This honestly feels like the worst game jam entry I've made so far, because half of the game is inaccessible, which sadly means that half of the art that the wonderful artist I worked with isn't even really in the game.
Still hope you'll enjoy the half that does (kinda) work, I had a lot of fun working on it :)
The agreed upon plans for multiplayer were mostly to pit robots of different users against each other in a fight, which would run locally (so the server would just distribute the programs to each player), if I recall correctly.
(I was the one who made the programming language happen for the most part, and I'm really used to languages with semicolons, mostly Rust XD)
Building the scripting language was definitely fun, thanks for letting me join the team!
(though C# sucks for programming language development and/or I'm just way too bad at that language XD)
> MonoGame is a free C# framework used by game developers to make games for multiple platforms and other systems.
I'm really not a fan of C#, to be honest. But maybe next year goodwebgame (Rust library) will be stable enough that I'm willing to use it in a gamejam, because then it'd work both in HTML5 *and* natively. (Last years entry used quicksilver, which is *okay*, but it had some weird issues that I needed to essentially work around in code)
Also, SFML is actually cross platform, if you don't need mobile & online :]
It is insanely hard to move anywhere, even after your plan of attack is over because all enemies are dead, mostly because there are not enough grey tiles (or I just don't fully understand the game).
Apart from that, it's absolutely brilliant. Love it :]
They will literally keep protesting countermeasures while protesters around them fall over dead.
I simultaneously love this game (it's well made, has more charm than it has any right to) and hate it (people protesting masks during a pandemic shouldn't be a thing).
Would've loved better messages at the end though for when you kill more than half the population, for instance.
Might be because I'm running it via Wine, but it appears to be broken in a few places (some levels immediately complete, for instance).
But I do have to say that I absolutely adore the art style!
> Also full disclosure, the double jump is a bug haha, we believe it has to do with the coyote time being weird.
Absolutely brilliant ^^ It does help when playing though, especially considering that the checkpoints don't work. Happy little accidents and all that :)
I can't say I know what's going on, but it's fun either way.
I do have to note that there is no Linux binary included, and while the Windows one works with Wine, none of the text gets displayed.
I do have to note that "How does your game fit the theme? Pretty good" does crack me up.
Anyway, good game :)
(side note: It actually does not include any linux binaries, but it does work with Wine)
I think those things with the one block high walls were supposed to be checkpoints, would've been *really* helpful if they worked (maybe they do under Windows and Wine fucked up though). But apart from that, here's two tips for other people playing this:
· You can, in fact, jump twice.
· The platforms move when you jump.
This has some funky behaviour when run under Linux with Wine, specifically, as soon as you defocus the game (which happens quite easily for me because I have two monitors), it will stop responding to inputs.
I saw "The E" at the end before I managed to get my mouse on the other screen again, and managed to get every single cube there. I hope that counts as a win.