Activity

Kolin63

Oh boy have I done a lot of work.

I already have 9 hours logged, but I haven’t even touched the gameplay yet. I’m really working hard to get the engine perfect and expandable.

Endian is going to be very similar to another discord bot MMO game I made before called Adriencoin. Both are in C++ and made with the Discord bot library D++ so there are no worries of me having trouble or having to learn about any of that.

However, I have never made a game engine like I am going to make for Endian. Endian’s engine (Engian? That would be a fun name) will be very data-driven, meaning that I will be able to add commands, items, locations, spaceships, etc. by just writing JSON. The code will then be written in C++ and compiled to WASM, so that it can be ran in a safe and sandboxed environment.

As you can see in the photo attached below, I have made some decent progress on making the mods load. I start the server with the instance called test (I really wanted to make it easy to use different instances because it was a pain while developing Adriencoin having to switch between release and development modes). You can see that the instance directory is properly selected, and then it scans the mods folder. It finds the base mod (endian-base) which has one namespace inside of it (endian). It then starts up the discord bot.

That is all it does for now. My next plan of action is to make the discord slash commands fully data driven which will be fun.

Attachment
0
Kolin63

Shipped this project!

Hours: 1.37
Cookies: 🍪 12
Multiplier: 9.08 cookies/hr

This was very easy to make, but its simplicity is what makes it great. It is exactly what I needed to forever improve my Linux experience.

Speaking of Linux, I know that this will be hard to review because there is no Windows support. For those who are not blessed with using a superior operating system, I hope that the GIF which I recorded will be enough of a demo experience.

Kolin63

This all started when I wanted to configure the Linux open command so that I could open png files in my web browser rather than the image viewing program which I did not really like. It turns out that this configuration process is convaluted and difficult and was not fun at all.

Therefore, I decided to create Pigpen, a wrapper around the open command. It is very simple because it is just a wrapper. It reads from a config file (located at $XDG_CONFIG_HOME/pigpen/config.txt) and decides what program to use.

In the below screenshot, you can see Pigpen in use. In the terminal window, you can see that my config has PDF’s open in Zathura and image files open in Qutebrowser. I then use Pigpen to open the monkey picture and it opens in Qutebrowser, and I use Pigpen again to open a D&D character sheet and it opens in Zathura.

I made Pigpen to be super easily configured, and I am very glad with how it came out. From now on, I will have “open” aliased to “pigpen” in my bashrc so I will always use Pigpen. If you want to use it too, I will have installation instructions in the Readme.

Attachment
0