#hours of code

The first couple days were continuing with my Minecraft mod, finishing up the amethyst materials in order to make way for my next gem. That was the first hour - imaging the tools in GIMP, writing their code, generating the JSON files, and finally compiling it all together to make sure everything is running. 

And, as it has been the past week, everything went smoothly - until I really began testing the results.

[ To preface: my testing up until this point has been rather lackluster. Basically I would just make sure the items appeared in the creative tab, had the correct texture, and the proper crafting recipe. ] 

This time, I decided to do a full test in vanilla. Giving myself some basic items, I found a vein of the amethyst ore in a cave and started mining with my ruby shickaxe. Boom. Problems. 

Turns out the shickaxe tool I was so proud of a few weeks ago has a few issues with custom blocks. It will mine vanilla ones as expected, but anything beyond that leaves a little to be desired. 

Y U DO DIS!? 

So what was expected to span a day turned into a running tally. I spent two hours the next day working on it, trying everything I could think of in both the shickaxe and ore files to make it work. 

[ Side note: I find it amusing that, given how much I complained Minecraft didn’t allow me my usual preference of test-driven development, the only way I’ve been able to figure this out is make tiny changes to the code, compile and see if it works. ] 

So far nothing I’ve tried has worked. I’m considering reworking the entire code for the shickaxe to see if that fixes anything, or perhaps (if it comes to it) scrapping the idea all together and just making individual pickaxes and shovels (though I have no guarantee those will work either.) 

Ahh Minecraft. Just when I thought I had you figured out. 

But the next day, fueled by my frustration, was incredibly productive. I jumped back to AlexaWeb and started to fill in some of the missing elements. 

The first was my “About Me” section. Despite having to write (or speak) about myself at least a few times a year, I never quite know what to say. Hey, I was a journalist - I’m used to writing about other people’s accomplishments. 

But with the help of NPR’s This American Life and a nice, cold soda, I eked out a couple paragraph/sentences about myself. Again, the entire thing is still in it’s formation stage, but I’m rather pleased as it stands. 

TLDR: Look at me! I can adult! Or at least write coherrently coherently. 

To take a break from writing words and go back to writing code, I played around with the footer of my page. I’m still finding a good spot to put my email (mailto links aren’t working with my laptop, so I have no way of testing whether or not they work) but I was able to link my GitHub and LinkedIn pages nicely. 

All and all, I’m still chugging along. The next couple days will be rather interesting as I finish this project while simultaneously moving into my senior year of undergrad. My goal is to have my website completely finished, or at least to a final draft. 

While I’ve been thinking about new content to add to the game, this latest update has been mostly implementing ideas I had earlier this summer. Namely: amethysts!

Much purple. Very hard to spell correctly. Wow.

Continuing with my gems trend, I chose amethyst namely due to the colour. The process was exactly the same as creating the ruby materials, with the added pressure that I rewrote the word four or five times before finally caving and googling the proper spelling. It took a bit of effort.

amythest, amethest, amythyst, amythist, ...

The second hurdle was dealing with the custom ore generator - but once I (with help) realized I was trying to spawn an ungodly amount of ore blocks at the same time and crashing my game, that, too, passed easily.

Once these were dealt with, actually creating the components were rather easy, and I began poking at some of the methods to see what else I could change. Ah-ha! Ore drops.

Previously, the method responsible for the number of items (rubies, amethysts, etc.) was hard-coded to one. In vanilla Minecraft, diamonds (what I’ve been loosely modeling my gems after) drops between 1-4 diamonds per ore block. So I quickly set up a rng and reset the drops.

Not pictured here: the 10 minutes it took me to realize my original code allowed an ore to drop nothing, and my subsequent rush to fix it.

Next I started working on the tools made of the gems. As of now I have a ruby axe and hoe, and an amethyst sword.

Again not pictured: my joy in discovering I don’t screw up the JSONs anymore.

Even more than that, I finally got around to creating custom tool materials, rather than relying on the vanilla emerald (for some reason diamond-level materials are classified as emerald in the code.) Both ruby and amethyst lie between iron and diamond in terms of stats, with amethyst being just a twinge better.

As always there are a bunch of things I still want to add - the rest of the amethyst items, modifying the axe to mine faster onLeftClick, adding more gems such as sapphires and actual emerald tools.

When I last worked with this code, I was struggling with some aspects of CSS and how they interacted with my subgroups (Projects and Music.) So that was where my work began. As usual, it took quite a bit of trial and error, but once I figured out how to pull the proper strings, setting up the rest of the page was relatively easy. 

Look! Actual website! With pictures!

After finishing the rough layout, I set my sights next on the music section. While having some description of the instruments I play and the work I’ve done will be nice, I really wanted to incorporate actual media. 

After some searching, I found Cincopa. It seemed pretty easy to customize and even easier to add to the site, so I uploaded a couple of my songs to test it out. After pushing the update to Github, I refreshed the page and was pleasantly surprised to see everything working. More or less. 

While the colours do go with my overall theme, it’s safe to say I’ll never make a living as an interior designer. 

The update thus far. It still need some work, but I really like how it’s coming together. 

The original concept had us reading in the song information from a file, storing it in an ArrayList, and using that information (with some input from the user) to create a playlist based on genre, artist, or mood. 

I wanted to keep a lot of that structure and add more, so my first step was to grab the old code and see what I could run of it. 

Not much apparently. 

After fixing the initial mini-bugs that always come with importing an existing project, I realised there was a huge issue with the Player I used to actually play the file - in short, it did not exist in my library. 

Do you want bugs? This is how you get bugs.

Apparently in my haste to get something working for the Hackathon, I found an older library called javazoom that worked with media files. After some googling, I found the site but as it was last updated in 2010, I figured there had to be other, more recent libraries to explore. 

And I was right. Kind of. 

After much digging, I came across javafx. Truthfully, I’m not sure of its full scope, but it does have a media player and related functions, and a rather nice API. So I started tinkering around with it, eventually figuring out how to play a song. 

Yup. It was Taylor Swift. Because my taste in music rocks. 

At first things were going up. I rearranged the code into a semblance of structure and began poking at the other methods trying to see what else worked. (Including figuring out how to control the sound - after nearly blowing my ears out, twice!) 

Unfortunately that’s where my progress has stalled. With the exception of pause() and stop(), the methods are less than obvious and when I went to run a full song as my last test, I discovered it stops after about 30 seconds. 

At least it’s pretty? 

I’m going to continue working on it, though I am serious considering reverting back to javazoom. I’d rather have well-written code using a slightly out-of-date library than mediocre stuff written with more modern equipment. 

I did work more on the encryption project, finally adding Scrambling in with the rest of the methods. I managed to combine the two from my testing class into one, using nested for loops to 1. select the individual word of the input, and 2. run the scrambling technique on it. 

I also fixed the main a bit, adding a loop and doing some basic input-checking. Nothing to write home about, but it made the output look a little nicer. 

Now all I need to do is put it in a terminal window. Then it could be in a tv show about “hacking”. 

The efficiency is not exactly what I’d like it to be. Having those nested for loops means I’m running through every single bit of information -  O( n2 ). In the context in which I learned efficiency - primarily searching -  a O of that would be terrible (i.e. Selection Sort.) But is that still true in this case? Thinking about it, hitting every node when trying to scramble a word all but guarantees the original word won’t remain when it’s done. 

But despite that, the original problem still remains - as n increases, the runtime of such code will as well - in theory punishing the user for wanting to encrypt a longer message. 

I’ve been doing some research on this and some java OO design principles. I’m still looking to add on to this project, but at the moment I’m not sure what direction that will be in. Restructuring everything into classes? But how to implement that? Perhaps start adding more UI elements? 

After the fun that was Windows 10, I finally got my Eclipse workspace up and running and decided to continue work on my Encoding project. I’ve put the Public/Private key stuff to rest for now - the theory still fascinates me, but I haven’t quite figured out how to implement it yet. 

Instead, I decided to work off of my Transposition method - but rather than simply reversing the input, it scrambles every word. It’s a pretty common mode of encryption, albeit generally rather simple to decrypt, and can be implemented with or without using spaces. (I kept the spacing, though am planning on making it an option later.)

Formatting the input was rather simple, but I ran into some problems when it came to actually scrambling the string(s) efficiently. My first instinct (remnants of my introduction to programming a few years ago) was to create a bunch of variables and basically hard code the “randomness” into the shuffle. I know enough not to go with this idea, but coming up with something a lot better is still a skill I’m developing. 

After thinking of a few options and following up with some hunches, I stumbled upon the Fisher-Yates shuffle. It’s pretty simple, looping through a character array and using a RNG to grab a character at random and exchange it with another. 

All in all, it looks like this:

And all with actual comments!? I should frame this!

As I have been the past thirteen days, I opened up Eclipse this morning and chose the workspace that hosted my Encoding project, wanting to spend a bit of time on that. Error. 

Wait, what? 

I tried again, and once more just to make sure I wasn’t doing something crazy. Then I checked the folder itself - it was set to read only. Okay, not hard to deal with. I unchecked the box, waited for it to process, and opened the workspace again. 

Same error

Long story abridged, apparently there is a bug (feature) in Windows 10′s security settings that sets all of your folders to read only, and that can’t be undone simply by unchecking the box. So, after hours of googling the issue (no help) and poking around in the settings, I starting looking into the permissions of users on my laptop. Changed a couple of them that didn’t seem like they would affect anything and voila - everything magically works. 

Ironically in saving this picture, I realized I needed to do the same for my Pictures folder. Good job.

This issue aside, I’ve actually quite enjoyed Windows 10 thus far. The interface is simple and (once customized) really easy to use. I’m still getting used to finding all of the settings/control panel options, but that’s with any new system. 

Plus with the personalization options, I can make it look like this. 

After many hours of caffeinated research (and a little help from a wonderful person) the mystery of the Shickaxe has finally been solved. We ended up creating an entire new template class that extended ItemTool and customized it to break the blocks we wanted (namely those that are normally broken by pickaxes and shovels.) 

On the plus side, this gives us a lot of flexibility into extending this class to make new items in the future - such as including the properties of an axe.

But, as with much of Minecraft’s code, figuring out how to do this was a pain, which does not bode well for the other things I want to begin including in this mod.

What you don’t see is that these lines go on horizontally for awhile...

The second part of this was creating the ruby shickaxe. Extending the template class and putting it through the game registry is second nature at this point, but I once again ran into issues with the JSON generator. You’d think after two months I’d know how to get it right the first time, but eh, details. 

This was the final design - 

Plus a custom crafting recipe - I’m on fire!

I’m still finishing up the ruby items, but with this success, I’m considering branching out into other joint tools - a shovel/hoe combination perhaps? 

My next mod project will also take a bit of research to make possible - a toaster. It’s simple, but I like toasted things in real life, and I like the idea of a mini-oven that would take fewer resources than an oven, but would still provide more hunger bars than raw.