Good vs. Evil
- Thread starter Randomguy404
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
11 and the new arena keeper code base is also on github https://github.com/lenscas/arena_keeper_quick
11 and I made a simple point/coordinate struct.
It isn't much but it allows me to more easily work with coordinates as I used to just use tuples and it has some nice functions already. All of which are subjected to automated testing using doc tests.
Now, time to expand the PointWithItem struct to expose similar methods as the point struct. Just with also exposing a way to set the contained item and stuff. I probably should also look if I can easily implement .map and all that fun stuff on it
It isn't much but it allows me to more easily work with coordinates as I used to just use tuples and it has some nice functions already. All of which are subjected to automated testing using doc tests.
Now, time to expand the PointWithItem struct to expose similar methods as the point struct. Just with also exposing a way to set the contained item and stuff. I probably should also look if I can easily implement .map and all that fun stuff on it
11 Its nice how the file containing the point structs (https://github.com/lenscas/arena_ke...ed3ce7202b64d53ea2d91a62/src/structs/point.rs) is more documentation and examples than code yet writing all that didn't feel like a waste at all as those examples also work as tests.
11 so... it turns out that the code I copied to create diagonal lines is bugged. It also turns out to not exactly be the easiest algorithm to implement so I may decide to just remove it all together.
As a work around I just decided to limit the player to selecting horizontal and vertical lines only. Also, I added code allowing the player to place "walls". So.... here is a picture of how the "game" looks right as of now:
the white square is supposed to be the square that your mouse is hovering over. No idea why it isn't covering a whole square, that somehow broke when making the screenshot.
the indigo lines= walls that are placed
orange =ground/dirt
green = grass
blue=water
gray = stone
next on the list is to add random terrains, rather than this rather obnoxious pattern that I only used so I could test if scrolling and zooming worked.
After that, a way to place characters which move around randomly. Then, making them unable to move through certain cells.
Also, fix that weird mouse position problem......
As a work around I just decided to limit the player to selecting horizontal and vertical lines only. Also, I added code allowing the player to place "walls". So.... here is a picture of how the "game" looks right as of now:
the white square is supposed to be the square that your mouse is hovering over. No idea why it isn't covering a whole square, that somehow broke when making the screenshot.
the indigo lines= walls that are placed
orange =ground/dirt
green = grass
blue=water
gray = stone
next on the list is to add random terrains, rather than this rather obnoxious pattern that I only used so I could test if scrolling and zooming worked.
After that, a way to place characters which move around randomly. Then, making them unable to move through certain cells.
Also, fix that weird mouse position problem......
10 generating the terrain may be harder than I hoped it would be.....
I found a crate that implements various kinds of noise algorithms. I was hoping I could just use those as if but clearly, I can't.
For those interested, the crate that I use is https://docs.rs/noise/0.5.1/noise/#structs
and my code to turn the returned floats into my terrain types is:
I found a crate that implements various kinds of noise algorithms. I was hoping I could just use those as if but clearly, I can't.
For those interested, the crate that I use is https://docs.rs/noise/0.5.1/noise/#structs
and my code to turn the returned floats into my terrain types is:
Code:
let num = num +1.0;
if num <=0.5 {
CellType::Water
} else if num > 0.5 && num <=1.0 {
CellType::Grass
} else if num > 1.0 && num <=1.5 {
CellType::Ground
} else {
CellType::Stone
}
10 I knew that, I just didn't know how to work with the noise functions that I had access to.
In other news, this felt so good to do: https://github.com/lenscas/arena_keeper_quick/commit/a6831327bea8575733c177813b4f272184d684a6
(Its a massive shift of code)
In other news, this felt so good to do: https://github.com/lenscas/arena_keeper_quick/commit/a6831327bea8575733c177813b4f272184d684a6
(Its a massive shift of code)
10 and I now have a square that walks around semi randomly on the map. It can not go through walls and its speed is depended on its own walk speed and the cell type that it is currently standing on.
edit: I decided to deploy the project to github pages. https://lenscas.github.io/arena_keeper_quick/index.html
edit: I decided to deploy the project to github pages. https://lenscas.github.io/arena_keeper_quick/index.html
Last edited: