Random Terrain Generation and Client Communicator #27
Conversation
.gitignore
Outdated
| Properties/Resources.resx |
There was a problem hiding this comment.
Do we still want these in our .gitignore?
|
|
||
| void LoadTerrain() | ||
| { | ||
| SQLiteDataReader results = DatabaseManager.ReadDB("SELECT * FROM Terrain;"); |
There was a problem hiding this comment.
Later we should probably just have functions in the DatabaseManager that would be called instead of writing SQL so we can keep the SQL contained there, but for now it's fine.
There was a problem hiding this comment.
The backend is going to be requesting and writing liberally, i don't want to have to be constantly making custom function wrappers in DB manager when i can just directly call it.
Backend/WorldData/Map.cs
Outdated
| TerrainData selected_terrain = terrains[0]; //This is probably not very good. | ||
| foreach(TerrainData d in terrains) | ||
| { | ||
| if (height > d.heightMax || height < d.heightMin) continue; | ||
| selected_terrain = d; | ||
| break; | ||
| } | ||
| terrainMap[x, y] = selected_terrain; | ||
| } | ||
|
|
||
| public void GenerateImage() | ||
| { | ||
| for(int x = 0; x < mapwidth; x++) |
There was a problem hiding this comment.
To keep things tidy we should have consistent variable name styling. Personally, I prefer camel case lettering, but I'm open for any type as long as it'd be consistent. In this highlighted section there is selected_terrain, heightMin and mapwidth. Not a crazy big deal for now & we can work on going through this later to update the styling if need be.
There was a problem hiding this comment.
i mix and match how i feel. consistency is for nerds. (Camel works)
#15 -This is already done, and more fixed.
#5 -Also done
Does #7
Very rudimentary but enough to divide and modify from here on out.
Also creates the Client Communicator, the device in which the frontend can call actions on the backend in an asynchronous way.