Newsletter 42: Jan 2023
AngelOnFira opened this issue Β· 13 comments
Newsletter 42: Jan 2023
tags: newsletter
Editors: @AngelOnFira, @ozkriff
Another month has gone by, so it's time to put together the Rust Gamedev newsletter with TODO's news!
Current Schedule
The soft deadline for all section PRs is 10 Feb 2023.
We may still accept PRs that are submitted later than this, as long as they're ready before the newsletter's release, but this isn't guaranteed. If you want your section to be included, don't leave it till the last minute!
How to Contribute
If you want to help writing the newsletter:
- Read CONTRIBUTING.md.
- Choose one or more of the "π free" sections listed below, and leave a comment letting us know you want to work on them.
- The links in brackets (like "1, 2, 3") are suggestions of links to include in the section. Feel free to add more!
- The username listed next to the section (like "@ozkriff?") is a suggestion of who may want to pick up the work (usually the project's developer, or someone who has expressed interest in the past).
- You are not obligated to write a section if you're tagged or your project is listed! You're welcome to ask someone else to write the section, or to ask for your project to be excluded from this month's post.
- Extra sections not listed in the plan are welcomed - just leave a comment and open a PR!
- Write a short overview in the newsletter's Markdown file, making sure to follow the style guidelines (see below).
- Send a PR to the
source
branch (example: #336). - Mention this issue in your PR's description to link it all together.
Style Guidelines
The full style guide is in CONTRIBUTING.md, but here are the most important rules:
- Write in third-person perspective.
- Each line must be 80 characters or less, for ease of reviewing/diffing.
- Only one image per section is allowed.
- The maximum size is 300kb for static images and 2.5mb for GIFs.
- The image should come before the text, and must have alt text for accessibility.
- Prefer static images to GIFs, to keep the page load times down.
- Each section should be under 1000 characters, and under 6 paragraphs.
- This only applies to the rendered text, not the markup.
- Keep formatting minimal - no bold/italics/etc.
- Avoid long/nested bullet point lists - no changelogs!
Please use these templates as a starting point:
Games/apps/libraries:
### [Game name]
![alt text](img)
_optional image label_
[Game name] ([GitHub], [Discord], [Twitter]) by [@nickname]
is... {short project description in one sentence}.
{An overview of the recent updates with links to more details}.
_Discussions: [/r/rust_gamedev](link), [Twitter](link), [etc](link)_
[Game name]: http://example.com
Articles/blog posts/videos/etc:
### [Article name]
![alt text](img)
_optional image label_
[@nickname] published an [article] about...
{overview what the resource is about}.
_Discussions: [/r/rust_gamedev](link), [Twiter](link), [etc](link)_
[Article name]: http://example.com
Current Structure & Status
Below is our current planned structure for the newsletter, and the status of each PR (which we'll try to keep updated).
This is not an exhaustive list - if you have your own project that you want to write about, just make a comment on this issue and open a PR!
Rust Gamedev Meetup
- Details of this month's meetup - π§ WIP by @AngelOnFira
Game Updates
- Veloren (1) - βοΈ done by @AngelOnFira
- Hydrofoil Generation (1) - π free (@kunos?)
- Tiny Glade (1) - π free (@anopara?)
- Thetawave (1) - π free (@cdsupina?)
- 8bit Duels (1) - π free (@ThousandthStar?)
- Cargo Space (1, 2) - βοΈ done by @johanhelsing
- Combine And Conquer (1) - π free (@I3ck?)
- Your Only Move is Hustle (1) - π free (@uzkbwza?)
- Digital Extinction (1) - βοΈ done by @Indy2222
- TheGrimseyβs devlog (1) - π free (@TheGrimsey?)
- Flesh (1, 2) - π free (@Im-Oab?)
- DGS (1) - π free (@Dominux?)
- Idu (1, 2, 3, 4) - βοΈ done by @logicsoup
- triverse (1) - π free (@bcarruthers?)
- Combine And Conquer (1) - π free (@I3ck?)
- Fish Folk: Punchy (1) - π free (@erlend-sh?)
- Life Code (1) - π free (@pinkponk?)
- digg (1) - π free (@Defernus?)
- Revolver Time (1, 2) - π free
- canal mania (1, 2) - π free (@lee-orr?)
Learning Material Updates
- Native iOS Touch Events w/ Rust (1) - π free (@wadez?)
- Bevy Basics video series (1) - π free (@PhaestusFox?)
- Platformer in Bevy video series (1) - π free (@PhaestusFox?)
- Introduction to the Entity Component System (1) - βοΈ done by @theredfish
Engine Updates
- fyrox (1, 2, 3, 4) - π§ WIP by @mrDIMAS
- alkahest-rs (1) - π free (@AnthonyUtt?)
- godot-rust (1, 2) - π free (@Bromeon?)
- piston (1) - π free (@bvssvni?)
- petrichor64 (1, 2) - π free (@Auxnon?)
Tooling Updates
- Graphite - βοΈ done by @Keavon
- Foxtrot (1) - βοΈ done by @janhohenheim
- Ten Minute Physics (1, 2) - π free (@cerrno?)
- rgis (1) - π free (@frewsxcv?)
Library Updates
- wgpu v0.15, naga v0.11 (1) - π free (@cwfitzgerald?)
- raster_fonts (1) - π free (@teryror?)
- torchbearer (1) - βοΈ done by @redwarp
- nvtt (1, 2) - π free (@mijalk0?)
- oxidized_navigation (1, 2) - π free (@TheGrimsey?)
- Matchbox (1) - βοΈ done by @johanhelsing
- VPlugin (1) - π free (@AndroGR?)
- egui_glium (1) - π free (@emilk?)
- tween (1) - βοΈ done by @sanbox-irl
- scene-graph (1) - βοΈ done by @sanbox-irl
- direct-storage (1) - π free (@hasenbanck?)
- rustysynth (1) - βοΈ done by @sinshu
- big-brain (1) - βοΈ done by @zkat
- bones (1, 2) - π free (@elrend-sh @erlend-sh?)
- airsim-client (1) - π free (@Sollimann?)
- Rapier (1) - π free (@sebcrozet?)
- miniquad (1) - βοΈ done by @not-fl3
- bevy-magic-light-2d (1, 2, 3) - π free (@zaycev?)
- notan v0.9 (1) - π free (@Nazariglez?)
Other News
- Bullet points of any interesting news that doesn't have its own section - π free (@AngelOnFira?)
Discussions
- "Is it a good idea to start learning game development with rust?" (1)
- "Tech stack for a turn-based roguelike in Rust" (1)
- "Pain points using Rust for gamedev?" (1)
- "I want to make a game thatβs compatible with Nintendo switch" (1)
Publishing Steps
- Final review - by everyone
- Publish - by @AngelOnFira
- Post on /r/rust, /r/rust_gamedev, /r/gamedev, URLO, twitter.com/rust_gamedev - by @AngelOnFira
- Pin thread on Twitter - by @ozkriff
- Add comment links - by @AngelOnFira
- Add a draft of next month's newsletter - by @AngelOnFira
Hi, I'm the author of rustysynth. I found out about this newsletter through a GitHub notification that my name was included in this issue. Would it be possible for me to write a description of rustysynth?
@sinshu of course, we would appreciate a PR! Here are our contributing guidelines but don't worry about them too much, we'll fix all the style/formatting issues during the PRs review. :)
I'll comment on torchbearer
then π
I'll take Idu
Yeah I'll write something up on tween. I'm also working on a library called scene-graph
that i'd like to write up as well
hope its not too late, I'll take miniquad update!
I'll take Cargo Space and Matchbox. Cargo space is nearly done, matchbox hopefully within a day.
Is the newsletter a good place for this article I wrote? https://indiedevcasts.com/posts/ecs-introduction . If yes, should I put it in other news?
@theredfish yes! I've added to the "Learning Material Updates" group - feel free to send a PR with a full section!
Thanks @ozkriff I will send it soon !
Hi! I'm the developer for Petrichor64. I'm not sure how you figured out my github when the repo is currently private, good sleuthing! I would like to write an article but I'm slammed with dayjob/parent stuff this month. The rust side of project is also unfortunately closed source at this time, so the coding/api layer is entirely in lua. For this reason Im not sure the project belongs here or not, but I'd love to give some insight or tips with wgpu or something next time!