Newsletter 52: June 2024

[github-actions]

Editors: @janhohenheim, @AngelOnFira, @mamaicode

Another month has gone by, so it's time to put together the Rust Gamedev newsletter with June's news!

Current Schedule

The deadline for all section PRs is the 28th of June, 2024. Submissions after this date will be added to the next newsletter.
Our target release date is the 3rd of July, 2024.

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!

Game Updates

• #1529
• #1531

Learning Material Updates

None yet. Feel free to submit yours!

Engine Updates

• Bevy 0.14 RC by @alice-i-cecile? @janhohenheim can do this as well
• #1532

Tooling Updates

• #1528

Library Updates

• egui_ratatui: #1526

Other News

• Tiny Glade Developers Discuss Bevy, Proceduralism, Publishers & Cozy Games by @anopara and @h3r2tic
• Larian cinematics: A Top-Down look at our Bottom-Up approach in 'baldur's gate 3'
• #1530

Discussions

• https://dioxus.notion.site/Dioxus-Labs-High-level-Rust-5fe1f1c9c8334815ad488410d948f05e

Calls for Submissions

Social Media

• Reddit
• Lemmy
• Mastodon
• Twitter/X
• Hacker News

Discord Servers

• Rust GameDev
• Bevy
• Blue Engine
• Macroquad
• Fyrox
• LogLogGames (comfy engine)
• Spicy Lobster
• Rust Godot

Let us know if you also want to receive monthly reminders on your Discord server!

Publishing Steps

• Final review - by everyone
• Publish - by @janhohenheim
• Post together with next calls for submissions - by @janhohenheim
• Pin thread on social media - by @janhohenheim
• Add comment links - by @janhohenheim

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 @janhohenheim?) 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 PR: N15: A/B Street #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 160 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

[gold-silver-copper]

Hello, I think I would like to write about my library egui_ratatui
#1526

[boozook]

👋🏻 I wrote about latest huge update in my project. #1528
Could be great if anyone can check it for grammar or something, please.

[boozook]

I have a question. Why some necessary things are restricted such as inline html abbr tags?
Error MD033/no-inline-html Inline HTML [Element: abbr] there.

[janhohenheim]

@boozook I don't actually know why that specific lint is in there. Maybe it does not play nice with zola? @AngelOnFira do you know about that?

[caspark]

I am not certain if I need to specifically leave a comment here, but since others have done so: #1529 contains my game's update for the month.

[boozook]

@janhohenheim,

That lint is not needed. I've just checked it with both versions of zola - latest 0.19.1 and that you're still using v0.15.2 and it works perfectly.

I don't think avto-dev/markdown-lint@v1 has anything to do with zola. Quote from doc

Note: To allow specific HTML elements, use the allowed_elements parameter.

Rationale: Raw HTML is allowed in Markdown, but this rule is included for those who want their documents to only include "pure" Markdown, or for those who are rendering Markdown documents into something other than HTML.

I suppose could be great to add something like "MD033": { "allowed_elements": [ "abbr" ] } to your .markdownlint.json.