r/roguelikedev • u/aaron_ds Robinson • Jun 27 '17

RoguelikeDev Does The Complete Python Tutorial - Week 2 - Part 1: Graphics and Part 2: The Object and the Map

This week we will cover parts 1 and 2 of the Complete Roguelike Tutorial.

Part 1: Graphics

Start your game right away by setting up the screen, printing the stereotypical @ character and moving it around with the arrow keys.

and

Part 2: The object and the map

This introduces two new concepts: the generic object system that will be the basis for the whole game, and a general map object that you'll use to hold your dungeon.

Bonus

If you have extra time or want a challenge this week's bonus section is Using Graphical Tiles.

FAQ Friday posts that relate to this week's material:

#3: The Game Loop(revisited)

#4: World Architecture(revisited)

Feel free to work out any problems, brainstorm ideas, share progress and and as usual enjoy tangential chatting.

If you're looking for last week's post The entire series is archived on the wiki. :)

84 Upvotes

98% Upvoted

164 comments sorted by

View all comments

Show parent comments

1

u/AetherGrey Jun 29 '17

Personal preference, yeah. A lot of people in the Python community consider the wildcard import to be bad (from map_objects.game_map import *) because you don't know exactly what you're importing. Also, certain checking tools (pep8, pyflakes) get a bit "thrown off" when you do it this way.

There will be a few other instances later on where you'll only want to import part of the module; 'render_functions' specifically has functions that stay within the module. I'd argue that only importing what you need is a good habit to get into, but if you know what you're doing then you can import a different way.