Skip to content

Commit d49b111

Browse files
authored
Newsletter 11: Add Arsenal (#176)
1 parent 0a05771 commit d49b111

File tree

1 file changed

+38
-0
lines changed

1 file changed

+38
-0
lines changed

content/posts/newsletter-011/index.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,44 @@ still a work in progress, so contributions are welcomed!
156156
[tetra-040]: https://twitter.com/17cupsofcoffee/status/1275778769077317637
157157
[tetra-dist]: https://tetra.seventeencups.net/distributing/
158158

159+
### [Arsenal Game Engine][arsenal]
160+
161+
[Arsenal] is the concept for a 2D and 3D game engine that is fully integrated
162+
with [Blender] and built on a Rust core. The engine will be built around an
163+
entity component system ( probably [Shipyard] ) for its performance and game
164+
design advantages. The vision of Arsenal is to build an Open Source game engine
165+
that is suitable for games of any scale and that is easily approachable by a
166+
wide audience of both complete beginners and seasoned experts.
167+
168+
Arsenal currently has a [POC][ars_poc] working, but there is no support for
169+
adding custom game logic. The next major step for Arsenal is to get initial
170+
[scripting support][ship_script_support] in Shipyard. The scripting plan for
171+
Arsenal borrows heavily from the [Amethyst scripting RFC][amethyst_scrpt_rfc]
172+
with the first target scripting language being Python. Other languages that are
173+
candidates for being added later are be [Mun], Lua, and maybe other languages
174+
written in Rust such as [Gluon].
175+
176+
More information on the Arsenal development direction can be found in the latest
177+
Arsenal development [blog post][arsenal_update].
178+
179+
[Katharos Technology][ktech] has gone live on [GitHub Sponsors][ghs_ktech] as a
180+
means to fund development of the development of the [Arsenal] game engine and
181+
supporting Rust gamedev libraries and tools such as [GFX], and [WGPU].
182+
183+
[ktech]: https://katharostech.com
184+
[ghs_ktech]: https://github.com/sponsors/katharostech/
185+
[arsenal]: https://github.com/katharostech/arsenal
186+
[gfx]: https://github.com/gfx-rs/gfx
187+
[wgpu]: https://github.com/gfx-rs/wgpu
188+
[arsenal_update]: https://katharostech.com/post/arsenal-development-now-on-github-sponsors
189+
[blender]: https://blender.org
190+
[shipyard]: https://github.com/leudz/shipyard
191+
[ship_script_support]: https://github.com/leudz/shipyard/issues/96
192+
[amethyst_scrpt_rfc]: https://github.com/amethyst/rfcs/blob/master/0001-scripting.md
193+
[mun]: https://mun-lang.org/
194+
[gluon]: https://github.com/gluon-lang/gluon
195+
[ars_poc]: https://github.com/katharostech/arsenal/releases/tag/v0.1.0
196+
159197
## Popular Workgroup Issues in Github
160198

161199
<!-- Up to 10 links to interesting issues -->

0 commit comments

Comments
 (0)