Hello, This includes multiple changes:

1. updated cargo.toml file, to only use amethyst features that are required (much faster build time).
2. load items, enemies and consumables from ./assets/data/* files at startup.
3. updated item spawn logic, now accepts list of items with probabilities.

that's pretty much it ;)

For #28

I think this work should be reviewed and merged after the feature-hitbox2d branch is merged into cdsupina-dev since there is already a lot of changes happening to the enemy component, entities, and related systems that should follow the same patterns introduced in feature-hitbox2d.

The ron config and data files are currently not baked into the binary. When the build is compiled, the user should not have access to these files to modify.

https://www.reddit.com/r/rust/comments/m6a3yx/theta_wave_v014_foundations_update/gr6blwt/?context=3

$ ./space_shooter 
./space_shooter: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by ./space_shooter)

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"

Currently blasts will travel until they reach a "despawn line" at a y-value above or below the arena. This is effectively inifinite range. Let's make the game more interesting by adding a finite range to fired blasts by giving them a TimeLimitComponent.

This will also allow us to add items to increase range in the future.

This PR introduces a player item that repels incoming enemy projectiles. Since this touches several files, I've broken it down into two separate commits.

The first part goes through adding a Blast enum variant to the SpawnableCategory and attaching it to the player's spaceship component.

The second adds the actual item: BlastRepeller, which is responsible for turning on the should_repel field for the spaceship's attractor data for a Blast spawnable.

I'm super new to Rust so let me know if there's more info required. I have just cloned and run cargo run, but the program panics before a window opens.

Version: 3276c8e81de6397adf399ba56b3a4686ae43015e OS: Windows 10 rustc 1.48.0 (7eac88abb 2020-11-16) cargo 1.48.0 (65cbdd2dc 2020-10-14)

thread '<unnamed>' panicked at 'attempted to leave type `linked_hash_map::Node<u32, rusttype::gpu_cache::Row>` uninitialized, which is invalid', C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\mem\mod.rs:658:9
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4\/library\std\src\panicking.rs:483
   1: core::panicking::panic_fmt
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4\/library\core\src\panicking.rs:85
   2: core::panicking::panic
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4\/library\core\src\panicking.rs:50
   3: core::mem::uninitialized
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\mem\mod.rs:658
   4: linked_hash_map::LinkedHashMap<u32, rusttype::gpu_cache::Row, core::hash::BuildHasherDefault<rustc_hash::FxHasher>>::ensure_guard_node<u32,rusttype::gpu_cache::Row,core::hash::BuildHasherDefault<rustc_hash::FxHasher>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\linked-hash-map-0.5.2\src\lib.rs:174
   5: linked_hash_map::LinkedHashMap<u32, rusttype::gpu_cache::Row, core::hash::BuildHasherDefault<rustc_hash::FxHasher>>::insert<u32,rusttype::gpu_cache::Row,core::hash::BuildHasherDefault<rustc_hash::FxHasher>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\linked-hash-map-0.5.2\src\lib.rs:304
   6: rusttype::gpu_cache::Cache::cache_queued<closure-7>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rusttype-0.8.3\src\gpu_cache.rs:778
   7: glyph_brush::glyph_brush::GlyphBrush<tuple<u32, amethyst_ui::pass::UiArgs>, twox_hash::std_support::sixty_four::RandomXxHashBuilder64>::process_queued<tuple<u32, amethyst_ui::pass::UiArgs>,twox_hash::std_support::sixty_four::RandomXxHashBuilder64,closure-
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\glyph_brush-0.6.3\src\glyph_brush.rs:336
   8: amethyst_ui::glyphs::{{impl}}::run<gfx_backend_vulkan::Backend>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\amethyst_ui-0.15.3\src\glyphs.rs:368
   9: shred::system::{{impl}}::run_now<amethyst_ui::glyphs::UiGlyphsSystem<gfx_backend_vulkan::Backend>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\shred-0.10.2\src\system.rs:140
  10: shred::dispatch::stage::{{impl}}::execute::{{closure}}
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\shred-0.10.2\src\dispatch\stage.rs:111
  11: core::ops::function::impls::{{impl}}::call_mut<tuple<mut arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>*>,closure-0>
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\ops\function.rs:247
  12: core::slice::iter::{{impl}}::for_each<arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>,closure-0*>
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\core\src\slice\iter\macros.rs:203     
  13: rayon::iter::for_each::{{impl}}::consume_iter<closure-0,mut arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>*,core::slice::iter::IterMut<arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-1.3.0\src\iter\for_each.rs:55
  14: rayon::iter::plumbing::Producer::fold_with<rayon::slice::IterMutProducer<arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>>,rayon::iter::for_each::ForEachConsumer<closure-0>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-1.3.0\src\iter\plumbing\mod.rs:110
  15: rayon::iter::plumbing::bridge_producer_consumer::helper<rayon::slice::IterMutProducer<arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>>,rayon::iter::for_each::ForEachConsumer<closure-0>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-1.3.0\src\iter\plumbing\mod.rs:438
  16: rayon::iter::plumbing::bridge_producer_consumer::helper::{{closure}}<rayon::slice::IterMutProducer<arrayvec::ArrayVec<[alloc::boxed::Box<RunNow>; 5]>>,rayon::iter::for_each::ForEachConsumer<closure-0>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-1.3.0\src\iter\plumbing\mod.rs:427
  17: rayon_core::join::join_context::call_b::{{closure}}<tuple<>,closure-1>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\join\mod.rs:130
  18: rayon_core::job::{{impl}}::execute::call::{{closure}}<tuple<>,closure-0>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\job.rs:113
  19: std::panic::{{impl}}::call_once<tuple<>,closure-0>
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:308
  20: std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:381
  21: std::sync::rwlock::{{impl}}::deref_mut<core::option::Option<alloc::sync::Arc<rayon_core::thread_pool::ThreadPool>>>
  22: std::panicking::try<tuple<>,std::panic::AssertUnwindSafe<closure-0>>
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panicking.rs:345
  23: std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure-0>,tuple<>>
             at C:\Users\rhysv\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\src\rust\library\std\src\panic.rs:382
  24: rayon_core::unwind::halt_unwinding<closure-0,tuple<>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\unwind.rs:17
  25: rayon_core::job::{{impl}}::execute<rayon_core::latch::SpinLatch,closure-0,tuple<>>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\job.rs:119
  26: rayon_core::job::JobRef::execute
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\job.rs:59
  27: rayon_core::registry::WorkerThread::execute
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\registry.rs:681
  28: rayon_core::registry::WorkerThread::wait_until_cold<rayon_core::latch::CountLatch>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\registry.rs:665
  29: rayon_core::registry::WorkerThread::wait_until<rayon_core::latch::CountLatch>
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\registry.rs:639
  30: rayon_core::registry::main_loop
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\registry.rs:759
  31: rayon_core::registry::ThreadBuilder::run
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\registry.rs:56
  32: rayon_core::registry::{{impl}}::spawn::{{closure}}
             at C:\Users\rhysv\.cargo\registry\src\github.com-1ecc6299db9ec823\rayon-core-1.7.0\src\registry.rs:101
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Entities whose Motion2D components with a rigid_body property set to true should be able to neglect any forces exerted on it. So if entity 'A' collides with an entity 'B' with rigid_body, entity B's Motion2D component will not be affected by the collision.

After merging #44 we should remove the use of fire_blast and replace with spawn_blasts in systems/spaceship.rs

Relevant files:

• systems/spaceship.rs

• entities/blast.rs

For #27

I also added detection for hitboxes with an angle offset from lines up with the x and y axes. I used the separating axis theorem implementation in rust from this repository: https://github.com/JoelEager/Rust-Collision-Detector.

Currently, collisions between the player (Spaceship) and enemies are still handled using the old hitbox_collide function in systems/mod.rs. However, the hitbox data used in the function parameters come from their respective Hitbox2DComponents. I think that collisions between enemies and players need to be reworked in a separate issue and at that time they should be switched over to using the is_colliding function in Hitbox2DComponent.

The Enemy component currently stores data about its Animation component. We can clean up the Enemy component by only specifying this data for the Animation component that's added to the entity created for an enemy.

Relevant files:

• Enemy Component

• Enemy entity

Repeater boss is currently in the game but incomplete. Let's finish the boss by giving it the following behaviors.

• Block weak spot with arms
• Shoot blasts and maybe missiles
• Shoot laser from eye
• Adapt behavior if both forearms are gone
• Boss is destroyed when eye part is destroyed

Refactor abilities into "trait objects" https://doc.rust-lang.org/book/ch17-02-trait-objects.html#defining-a-trait-for-common-behavior

Character components can each have an ability property containing a struct that implements the ability trait. It would resemble the following.

pub struct CharacterComponent {
    pub ability: Box<dyn Ability> ,
    ...
}

Structs implementing the ability trait could share common functions related to cooldowns and execution.

Right now we need to manually delete the generated config folder that is responsible for containing some of the RON file assets.

It would be nice if we could run a script as part of the build process where it checks for any changes to the data_include/config folder and rebuild it with the new changes

Currently all formation spawnables are spawned in at once. Let's add the ability for formations' spawnables to be spawned in after a delay rather than all having to be spawned in at the beginning of the formation.

Here the log

[19:16:39] baba99j@baba /home/baba99j/Downloads/theta-wave
> cargo run --release
   Finished release [optimized] target(s) in 0.30s
   Running `target/release/theta-wave`
[INFO][amethyst::app] Initializing Amethyst...
[INFO][amethyst::app] Version: 0.15.3
[INFO][amethyst::app] Platform: x86_64-unknown-linux-gnu
[INFO][amethyst::app] Amethyst git commit: UNKNOWN
[INFO][amethyst::app] Rustc version: 1.51.0 Stable
[WARN][rendy_factory::factory] Slow safety checks are enabled! Disable them in production by enabling the 'no-slow-safety-checks' feature!
[INFO][rendy_util::wrap] Slow safety checks are enabled! You can disable them in production by enabling the 'no-slow-safety-checks' feature!
[WARN][rendy_wsi] Image count not supported. Supported: 4..=4294967295, requested: 3
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "Image count not supported." }

   0: failure::backtrace::internal::InternalBacktrace::new
   1: <failure::backtrace::Backtrace as core::default::Default>::default
   2: rendy_wsi::Surface<B>::into_target
   3: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::try_fold
   4: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
   5: core::iter::adapters::process_results
   6: <rendy_graph::node::render::pass::RenderPassNodeBuilder<B,T> as rendy_graph::node::NodeBuilder<B,T>>::build
   7: rendy_graph::graph::GraphBuilder<B,T>::build
   8: <amethyst_rendy::system::RenderingSystem<B,G> as shred::system::RunNow>::run_now
   9: <shred::dispatch::dispatcher::Dispatcher as shred::system::RunNow>::run_now
  10: <T as amethyst::state::State<amethyst::game_data::GameData,amethyst::state_event::StateEvent>>::update
  11: theta_wave::main
  12: std::sys_common::backtrace::__rust_begin_short_backtrace
  13: std::rt::lang_start::{{closure}}
  14: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /build/rust/src/rustc-1.51.0-src/library/core/src/ops/function.rs:259:13
      std::panicking::try::do_call
             at /build/rust/src/rustc-1.51.0-src/library/std/src/panicking.rs:379:40
      std::panicking::try
             at /build/rust/src/rustc-1.51.0-src/library/std/src/panicking.rs:343:19
      std::panic::catch_unwind
             at /build/rust/src/rustc-1.51.0-src/library/std/src/panic.rs:431:14
      std::rt::lang_start_internal
             at /build/rust/src/rustc-1.51.0-src/library/std/src/rt.rs:51:25
  15: main
  16: __libc_start_main
  17: _start
', /home/baba99j/.cargo/registry/src/github.com-1ecc6299db9ec823/amethyst_rendy-0.15.3/src/system.rs:117:18
stack backtrace:
   0: rust_begin_unwind
             at /build/rust/src/rustc-1.51.0-src/library/std/src/panicking.rs:493:5
   1: core::panicking::panic_fmt
             at /build/rust/src/rustc-1.51.0-src/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /build/rust/src/rustc-1.51.0-src/library/core/src/option.rs:1300:5
   3: <amethyst_rendy::system::RenderingSystem<B,G> as shred::system::RunNow>::run_now
   4: <shred::dispatch::dispatcher::Dispatcher as shred::system::RunNow>::run_now
   5: <T as amethyst::state::State<amethyst::game_data::GameData,amethyst::state_event::StateEvent>>::update
   6: theta_wave::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.