this post was submitted on 06 Aug 2023
14 points (100.0% liked)
Python
6357 readers
1 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
📅 Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django 💬)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
🐍 Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
💓 Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
✨ Python Ecosystem:
🌌 Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- Pythörhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’d recommend starting with a very small-scoped project that has some of the features you want to learn. Some images, some choices, branching dialog trees, resources, etc. depending on what it is you care about, pick a couple of things to focus on and make it very small scale. It’s easy to get overwhelmed, so having a small working prototype of something beginning to end (esp. something you can put together in days to weeks, rather than more time) is good for learning and something you can be proud of and look back on without getting overwhelmed with over designing and never finishing. I’d also recommend treating the project as the first in a long line of cool games you can make, instead of your magnum opus—again, trying to be a perfectionist with your first game can be very overwhelming and lead to you eventually giving up instead of getting your first game done. You can always go bigger later.
If it’s programming itself you are intimidated by, you might want to look into Twine or other interactive fiction tools to start off with—these should allow you to easily make choice based stories without having to worry about learning a bunch of coding off the bat.
Most of learning is just picking something you want to do, and finding other peoples examples of doing it and seeing how they do it—whether it’s showing unique sprites or implementing an inventory. Through this you make incremental progress learning. Don’t be afraid to search for examples and troubleshooting.
(Most of this is generic advice, sorry if it comes across as too basic but not sure what level your at — a lot of this is the same advice I give to my starting game design students. But coming from someone who is in game dev now and does programming every day, most of my learning is just searching “how to do X in Y [language/game engine] and learning to dissect stack overflow, examples, and documentation, plus following starter guides for new tools/projects in unfamiliar with). I’m not sure if there are more structured lessons or tutorials out there for the kind of game dev you are interested, but that could be worth looking into and following if you are easily overwhelmed or feel like you need more structure.
Good luck!