Thanks for the bug reports! I’ve fixed #2 and will put out an updated version once the voting period ends.
For #1, what specific issues did you run into with keyboard input, and on what browser? (If it’s specifically about using Tab to navigate through the menus, I can improve it a bit, but the UI library that I’m using has a number of bugs with keyboard navigation that I can’t easily fix.)
Firefox. There are multiple input fields for numbers. Attempting to edit them either pops up browser's search panel or (in case of backspace) goes back in browser history.
Thanks for playing! I could group packets (and will if the rendering becomes a bottleneck), but it’s currently doing some other absurdly inefficient things that should be easier to optimize. There’s a lot of low-hanging fruit for fixing the performance that I didn’t get to during the jam itself.
(The number one thing is improving the search for routes; whenever a node is captured, it has to traverse the whole graph and recompute every route, which creates lag spikes.)
Unfortunately I ran out of time before getting enemy AI into a workable state (and interactions between the player and enemies), so for now enemies don’t appear naturally.
If I continue working on this after the jam, I’ll aim to have a few type / factions of enemies that appear in clusters around the map. Factions would have basic AI with different dispositions; passive clusters that defend their own territory, active clusters that act like a player and grow, or aggressive clusters that seek out and attack the player.
(In theory this could also be generalized to make this a multiplayer game, with a lot more work.)
panicked at src/lib.rs:56:21: Error: Failed to acquire adapter
Error at imports.wbg.__wbg_new_abda76e883ba8a5f (blob:https://html-classic.itch.zone/4c703f83-12e7-404c-992a-39da139ad17f:419:21) at engine_demo.wasm.console_error_panic_hook::hook::h4150eac16ea3f9bc (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[3863]:0x78cd7a) at engine_demo.wasm.core::ops::function::Fn::call::h7a0e4d0f9cadb115 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[24982]:0xb5a556) at engine_demo.wasm.std::panicking::rust_panic_with_hook::h6731baa78621a747 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[10527]:0xa502d8) at engine_demo.wasm.std::panicking::begin_panic_handler::{{closure}}::hb6cd8464ed39ae71 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[12208]:0xaa508b) at engine_demo.wasm.std::sys_common::backtrace::__rust_end_short_backtrace::hbdf3ddeb21a1e747 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[24930]:0xb5a37f) at engine_demo.wasm.rust_begin_unwind (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[16352]:0xb16249) at engine_demo.wasm.core::panicking::panic_fmt::h5c7ce52813e94bcd (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[16957]:0xb1f98e) at engine_demo.wasm.engine_demo::run::{{closure}}::{{closure}}::h7788e4588d165c92 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[612]:0xc2254) at engine_demo.wasm.engine_demo::run::{{closure}}::h7c61492b0e18defc (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[2590]:0x65996a)
It looks like some versions of Chrome say that WebGPU is supported, but then fail when you try to use it. For now, the only real option is to use a browser that either has WebGPU enabled, or that doesn’t support WebGPU. Firefox should work, and recent versions of browsers on Windows should work. (My guess is that Chrome on Linux is the main browser that has this issue?)
I’ve patched it locally, but unfortunately I can’t upload the fixed build until the review period ends.
Uh, looks like I forgot to remove some logic! A blue node is created by right-clicking (which I forgot to remove, whoops), and you can re-capture it by left-clicking on it. Packets disappearing means that something in the gameplay logic crashed, which I'll try to fix once the uploads are unlocked.
← Return to game
Comments
Log in with itch.io to leave a comment.
Great game, beat it in two days, would love more :)
1) Game does not handles keyboard properly. Use preventDefault in the handling code.
2) Packets stops if #of targets for randomization 4 or 5. They return if # dropped below 4 or randomization disabled.
Thanks for the bug reports! I’ve fixed #2 and will put out an updated version once the voting period ends.
For #1, what specific issues did you run into with keyboard input, and on what browser? (If it’s specifically about using Tab to navigate through the menus, I can improve it a bit, but the UI library that I’m using has a number of bugs with keyboard navigation that I can’t easily fix.)
Firefox. There are multiple input fields for numbers. Attempting to edit them either pops up browser's search panel or (in case of backspace) goes back in browser history.
it gets a bit laggy late game (when you have taken over half the nodes) can you make a setting to cump the packets?
Thanks for playing! I could group packets (and will if the rendering becomes a bottleneck), but it’s currently doing some other absurdly inefficient things that should be easier to optimize. There’s a lot of low-hanging fruit for fixing the performance that I didn’t get to during the jam itself.
(The number one thing is improving the search for routes; whenever a node is captured, it has to traverse the whole graph and recompute every route, which creates lag spikes.)
How Do Enemy's Normaly Apear?
Unfortunately I ran out of time before getting enemy AI into a workable state (and interactions between the player and enemies), so for now enemies don’t appear naturally.
If I continue working on this after the jam, I’ll aim to have a few type / factions of enemies that appear in clusters around the map. Factions would have basic AI with different dispositions; passive clusters that defend their own territory, active clusters that act like a player and grow, or aggressive clusters that seek out and attack the player.
(In theory this could also be generalized to make this a multiplayer game, with a lot more work.)
Will you continue working on it to get the enemy AI in a working state? Would honestly love to see more from this game, pretty fun
I get an error in browser:
panicked at src/lib.rs:56:21: Error: Failed to acquire adapter
Error at imports.wbg.__wbg_new_abda76e883ba8a5f (blob:https://html-classic.itch.zone/4c703f83-12e7-404c-992a-39da139ad17f:419:21) at engine_demo.wasm.console_error_panic_hook::hook::h4150eac16ea3f9bc (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[3863]:0x78cd7a) at engine_demo.wasm.core::ops::function::Fn::call::h7a0e4d0f9cadb115 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[24982]:0xb5a556) at engine_demo.wasm.std::panicking::rust_panic_with_hook::h6731baa78621a747 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[10527]:0xa502d8) at engine_demo.wasm.std::panicking::begin_panic_handler::{{closure}}::hb6cd8464ed39ae71 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[12208]:0xaa508b) at engine_demo.wasm.std::sys_common::backtrace::__rust_end_short_backtrace::hbdf3ddeb21a1e747 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[24930]:0xb5a37f) at engine_demo.wasm.rust_begin_unwind (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[16352]:0xb16249) at engine_demo.wasm.core::panicking::panic_fmt::h5c7ce52813e94bcd (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[16957]:0xb1f98e) at engine_demo.wasm.engine_demo::run::{{closure}}::{{closure}}::h7788e4588d165c92 (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[612]:0xc2254) at engine_demo.wasm.engine_demo::run::{{closure}}::h7c61492b0e18defc (wasm://wasm/engine_demo.wasm-04255cde:wasm-function[2590]:0x65996a)
Thanks for the bug report!
It looks like some versions of Chrome say that WebGPU is supported, but then fail when you try to use it. For now, the only real option is to use a browser that either has WebGPU enabled, or that doesn’t support WebGPU. Firefox should work, and recent versions of browsers on Windows should work. (My guess is that Chrome on Linux is the main browser that has this issue?)
I’ve patched it locally, but unfortunately I can’t upload the fixed build until the review period ends.
After a blue node appeared all my packets disappeared and their count in the stats window only rose up
Uh, looks like I forgot to remove some logic! A blue node is created by right-clicking (which I forgot to remove, whoops), and you can re-capture it by left-clicking on it. Packets disappearing means that something in the gameplay logic crashed, which I'll try to fix once the uploads are unlocked.
Thanks for playing!