Do we have plans for adding an

EditorAction

for editing layers/objects? I'm starting to play around with the editor and it seems like it would be a nice addition when you want to rename layers/objects.

@User I'm not entirely sure why your PRs are stuck on a check. Perhaps you can close and then re-open them? It could be an issue on GitHub's end?

Trying that now.

It turns out that this was happening due to the protected branch (

main

) enforcing build checks for PRs whereas we skip those checks for certain files (

*.{md,json}

) so it gets stuck: https://github.com/fishfight/FishFight/pull/236#issuecomment-969247776

oh wow, nice catch! And thanks for documenting that in the issue 👍

any notes on https://github.com/fishfight/FishFight/releases/tag/untagged-e66b72d557dea3b316d7 ?

woooo, new release! what's the rollout plan 🧐

Getting a video of the editor made in the next few days, then we’re ready.

> It might be instructive for a tutorial follow-up: Custom UI. We should teach modders the basics of adding new UI to the editor or overall game experience. @Micah is gonna take this on.

@cdsupina any thoughts on what your next learning project might be? Lemme me/us know if you want suggestions.

One little thing we’ve got pending is a complete listing of all our weapons, including the ones that are specced out.

It improves discovery of the still-pending items that we wanna onboard contributors with.

Do you mean that we could expand on the items page of the book? https://github.com/fishfight/FishFight/blob/main/book/src/items.md do you mean we should add the items that are currently in the game to this page?

Also I was thinking of adding more branching examples of adding items to the game.

Currently we have a tutorial for the gun weapon, but I think it may make sense to provide some examples for throwable and melee weapons as well

I probably will just branch off of the sniper weapon tutorial where the differences matter

I’m saying we should add another section for “Pending” items, where we list any item that is in progress with a SPEC already.

Sounds good I'll work on that next

Do we have have any recommended .vscode settings for dev setup?

I've been using the Rust Analyzer extension for rust dev: https://marketplace.visualstudio.com/items?itemName=matklad.rust-analyzer .

that ☝️ +

"rust-analyzer.checkOnSave.command": "clippy",

There is this extension pack that I think it's pretty neat, has some nice extensions: https://marketplace.visualstudio.com/items?itemName=nyxiative.rust-and-friends

Let’s commence some open discourse on Book structure.

First of all, we might wanna go back to using book.fishfight.org for that particular product, because that’s what it is. It’s more important for the Learning team to default to that more general term, as the Book may not always be this team’s primary project.

TODO: Add various more “stickers” to our repo. Example:

TODO: Add a list of most important links high up in the readme description.

We should consider some new and exalted primary sections..

1. Fish Fight: Universe - Community - Gameplay wiki - Modding - Contributing - Releases - Roadmap 2. Fish Fight: Dev - Architecture.md - Mechanics - Netcode - Juice - Editor - Builds 3. Fish Fight: Platformer - how to make Platformer games in Rust (possible collab with PragProg.)

Book structure

This needs to be a redirect or smt