@Mannan-15 Thanks for the PR! The changes look fine, but I think the build is failing based on our recent repo name change. Let me look into that real quick so we can ensure your PRs passes its tests.

Thanks for the review @tpike3!

Glad to hear the changes look good. I'll wait for the CI/CD build issues to be resolved.
In the meantime, are there any other specific issues (in mesa or mesa_llm) that you would recommend? I'm eager to keep contributing while this gets merged.

@Mannan-15 As the build failures do not involve your code i am going to merge this. As for things to do I would engage in the mesa-llm repo and with that team. As llm's are very popular mesa-llm has a lot of people engaged so I would definitely work with them to find a spot they need contributions.

One thing mesa really needs is its examples repo updated so they reflect 3.3. An AI area to start would be the reinforcement learning integration if you want to learn about multi agent reinforcement learning. If you do examples please ping us in the chat https://github.com/projectmesa so we know you did it.

Thanks for the merge @tpike3!
I’ll definitely engage with the mesa-llm as you suggested.
Regarding mesa-examples, I'm very interested in the multi-agent reinforcement learning integration. I plan to work on developing new examples that utilize Mesa 3.3 capabilities and start prototyping the RL integration features.

I'll make sure to ping you in the chat once I have some progress to share. (but the link you provided seems to redirect to the wrong page).

This PR broke our CI and the tutorial for most users:

• Tutorial: Cell capacity enforcement breaks tutorial when agents exceed capacity #2962

As the build failures do not involve your code i am going to merge this.

While for the build failures this was true, it unfortunately wasn't for the Readthedocs failure.

But it helped discover an imperfection in both our cell movement handling, so hey.

Ah, thanks for catching that @EwoutH! Sorry about the tutorial breakage, but I'm glad it at least helped surface the edge case in the movement logic.

Thanks for handling the fix. I'll keep an eye on the discussion in #2962 to see how the capacity handling evolves.