xenonlab-studio / terracraft Goto Github PK

It would be useful to have the game labels (fps and coords) of white color with a transparent black background to have better readability.

In python3.8 time.clock() is removed, documentation says it must either be replaced with time.process_time() or time.perf_counter().

It seems that many of the open issues are already solved, and can be closed.

Now vertical flight up (space bar "and down (Left-Shift") is possible.

Run mode is now activated with Left-Ctrl.

The main.py module has become too big! I want to divide the classes and functions into various modules to make the project more organized and easy to manage.

Python 2 is maintained until January 2020, it is recommended to update projects before that date.

Python 3 is now mature, especially with the new version 3.6.4. In the PyCraft project there is no reason to keep the old code for Python 2.7.

Added global variables for display speed in the "settings" section of the code.

This will require writing some simple LightSource classes. OpenGL has a few different types of lights with logs of parameters. It will require a little bit of OpenGL knowledge to write these classes but, once written, will be easy to use to add lights emitting to different things.

Hi,
I found this handsome project a few weeks ago and started messing around with the code.

I found it very useful and I want to work on a project using it as a code base (but I will also rewrite most of the engins)

Is it okay if I use it?

All the constants to set the engine parameters are grouped in the "settings" area. This makes the project more orderly and easily configurable, especially in anticipation of a future main menu.

Add vertical flight capacity, by pressing the following command:

• Spacebar (up)

This is a very useful feature. PyCraft is a small sandbox game focused exclusively on creative mode, so vertical flight is very convenient for building structures.

This is important so TerraCraft will show up OK in the taskbar.
An image of 128x128 or so should be good.

The crosshair is no longer displayed. Probably it is no longer processed in the code? I check as soon as I can.

It's a good idea to exclude these folders. If anyone tries to contribute, it will interfere with their local versions.

New free textures, directly from my version of "PixelBox", texture pack for Minetest.

Added saving and automatic loading of the map. The Save/Load system has the following characteristics:

• Added saving of the game in progress by pressing the F5 key.
• Automatic loading at startup, if the file savegame.sav exists.

Jumping over the wall, the player no longer falls to infinity but is held at the position of 1 block relative to the lower badrock plane of the map.

Here is the result:

At some point, we can begin to add sound effects. For a start, we can use a site such as "jfxr" to generate some simple free samples. They can be exported as wav files: https://jfxr.frozenfractal.com/

For playback, the most simple way would be to:

1. Write a simplified AudioPlayer class, to wrap the pyglet.media.Player class. This class can have play and play_music methods to start.
2. Each Scene will have a reference to the audio player, so you can do something like: self.audio_player.play('jump.wav')` from any Scene.

This would be very simple and quick to add. To start, maybe we should rename /img to /assets? Then we can organize things into something like /assets/sounds and /assets/images. What do you think?

I've just made some small additions that can be useful.

Hide the GUI, or just the information for fps, the coordinates, etc. It is useful when capturing a screenshot or during development tests.

A suggestion -- a useful feature for education would be to allow students to write code that can add and delete blocks automatically. For example, I would like my students to be able to write a "game of life simulation" within terracraft. Maybe a new class of block -- a "control block"? Something like that?

It takes time to initially draw all the blocks (initial chunks), so I added a simple "Loading..." label that covers the center of the screen during the first design cycle.

Always better than having an empty screen waiting for the upload :D

In the future I want to create a semitransparent text frame to make the text more readable and visually beautiful (including the import of a new, well-readable pixelated font).

We will need to enhance the saving/loading features, and also easily share data betwen the different Scenes. I have a plan to do this, but I would like your feedback.

1. The SceneManager will gain a few dictionaries. This will include an "options" dictionary, containing things such as "fullscreen", "volume levels", etc. This will also include an "inventory" dictionary.
2. The SceneManager class will have a reference to the SaveManager. This means that all Scenes can access it (because all Scenes already have a reference to self.scene_manager).

In this design, the MenuScene can check the self.scene_manager['options']['fullscreen'] value to see if the game should be full screen. An OptionsScene could be used to set all of these things. When you are playing, you bring up the inventory Scene, and make some actions. The GameScene can see this data when you return to the game.

If it helps, I will make a pull request with the basic design. You can decide if you like it or not. As always, feel free to reject any pull requests you do not like.

I have performed the following corrections and improvements to the code:

• Font size from 18 to 12.
• Adding text labels (FPS + COORDS).
• Remove the round brackets, and add the square brackets.
• Added the ":" of separation.

It would be really great if we could separate the generate_world call from scenes.py! This would allow students to look at the source code and understand how proc. gen works -- but more importantly, it would allow them to write their own algorithms to generate terrain!

Blocks: Dirt, Grass, Snow, Sand, Brick, Badstone, are saved at startup correctly without problems.

the blocks: Tree, Leaves, Wooden_Planks generate an error that causes the program to crash!

I work on the bugfix, I suspect it is a variable that determines the maximum number of blocks? The original Michael Fogleman project only implemented Grass, Sand, Brick, Stone.

I focus on debugging!

WIP...

Mobs would be epic!

I was thinking that we should remove the "now loading" label from the GameScene. Instead of waiting for the level to be generated, we will want to add incremental loading. This will be important when we try to create larger maps in the future; it won't be practical to wait for the entire map to be generated. Also, when we implement a better generation algorithms, it will be better if we don't have to wait.

Make screenshots by pressing the F12 key.

Warning! Each time F12 is pressed, the previous screenshot is overwritten! I recommend saving each screenshot by adding a number.

Example:

screenshot_01.png

Note: that images can only be saved in the PNG format unless the Pillow library is installed.

Added the following blocks:

• Dirt
• Snow
• Badstone
• Tree
• Leaves
• Wooden_Planks

The block highlighting is currently a little strange looking, due to changes in my recent pull request. Please assign this to me, and I will fix it when I have some time.

I added possibility to switch player movement speed between walk and run (in no-flying mode).

I created the setup.py module to include the following information:

from setuptools import setup

setup (
     name = 'TerraCraft',
     version = '0.2.1',
     packages = ['pyglet'], # external packages as dependencies
     url = 'https: //github.com/XenonCoder/TerraCraft',
     license = 'GPL 3.0',
     author = 'Stefano Peris a.k.a. <XenonCoder> ',
     author_email='[email protected] ',
     description = 'Voxel Engine written in Python 3 + Pyglet.'
)

Very important if we want to distribute the project in the future (for example, in the ubuntu repository).

Correction of typos in comments.

This is a low priority bug, but we should fix it eventually.
Right now, we check if a save exists, and if so, we load it and skip the new map generation.
We should check if the save loads correctly, and then return a True/False result. If this happens, we can then generate a map.

The old Minecraft textures are not in line with the open source spirit of this project. I have edited new textures that are much more beautiful and free.

I made the following changes:

• It more apparent and player does not have to change his position to see the
  wall because it is built right in front of player.
• I Also changed the name of the build wall function from buildWall to build_wall this makes it more consistent with the variables and function names within the game.