JS13K Games 2019 Day 10
Don't worry! You're not missing anything! I just didn't do any work on this for about a week. I hope no one who manages Developers sees this and goes "There! That's why we have crunches!", "Developers are lazy!", or something. My real job has been really hectic lately. Plus, if I have to choose between losing this competition and keeping my paying job: I'm keeping my paying job. This was just something to do for fun and to break up the monotony of stuff I have to do for my job. Anyway, I did do some work on Shield Bearer!
I completed setting up my repository for Shield Bearer! I haven't wrote any actual code yet for the thing, but I did start planning out what all needs to be done. I brainstormed what needs to be done in order to "ship" the game. Those are things needs to be done in order for me to have a game that I could zip up and submit to be judged by the competition experts. Without them, I got nothing playable!
Then there are things that I would like to have to give the game an edge on the competition. I've called those things "Not so Critical". They're things that I don't need in order to have a working game, but I feel they would make my game interesting. There's also a focus on getting just the "Desktop" version of the game working, and one of the "Not so Critical" features is to have the same game working and playable in mobile as well. I did find some code on StackOverflow that will help me detect mobile browsers. That snippet of code should allow me to have stuff like a D-Pad and a couple buttons on the screen, but only have them show on mobile.
After those features, I have the "Nice to Haves". These are features that would really make my game shine, but they would detract from developing the actual game if I focused on them. So, I labeled them as such, so I can go after them when I have a playable product. These are features that would add some extra polish to my game. I think if I run out of time and don't get these features done, I might go back and use these features in a Turbo Edition or something. I do like how "Turbo Edition" feels like something you would add to a Classic Video Game: nice and retro. Yeah, the master branch will be what I got done (or tried to get done) for the competition, and I'll fork it and make a new branch for my polished "Turbo Edition"!
Also, I was researching ways to compress my source code down to that 13K zip file. The apps that I create at work have file sizes like 150K for one file of text. That one text file doesn't even run the whole application, as well! So, yeah, I really want to know how to compress my files for the competition. So I managed to find a page talking about open source JavaScript compressors! They're supposed to obfuscate my code, my it unfriendly to be read by humans, while compressing the file size by 40% to 60%. According to this article on zip files, 7-zip can compress down to 76%. If I did that and zipped it, then my total file size should be reduced by 54.4% to 69.6% (the math for that is compressorPercentage + ((1 - compressorPercentage) * (1 - zipCompression)), and that's taking what the compressor has done and using 7-zip to compress what was left).
I completed setting up my repository for Shield Bearer! I haven't wrote any actual code yet for the thing, but I did start planning out what all needs to be done. I brainstormed what needs to be done in order to "ship" the game. Those are things needs to be done in order for me to have a game that I could zip up and submit to be judged by the competition experts. Without them, I got nothing playable!
Then there are things that I would like to have to give the game an edge on the competition. I've called those things "Not so Critical". They're things that I don't need in order to have a working game, but I feel they would make my game interesting. There's also a focus on getting just the "Desktop" version of the game working, and one of the "Not so Critical" features is to have the same game working and playable in mobile as well. I did find some code on StackOverflow that will help me detect mobile browsers. That snippet of code should allow me to have stuff like a D-Pad and a couple buttons on the screen, but only have them show on mobile.
After those features, I have the "Nice to Haves". These are features that would really make my game shine, but they would detract from developing the actual game if I focused on them. So, I labeled them as such, so I can go after them when I have a playable product. These are features that would add some extra polish to my game. I think if I run out of time and don't get these features done, I might go back and use these features in a Turbo Edition or something. I do like how "Turbo Edition" feels like something you would add to a Classic Video Game: nice and retro. Yeah, the master branch will be what I got done (or tried to get done) for the competition, and I'll fork it and make a new branch for my polished "Turbo Edition"!
Also, I was researching ways to compress my source code down to that 13K zip file. The apps that I create at work have file sizes like 150K for one file of text. That one text file doesn't even run the whole application, as well! So, yeah, I really want to know how to compress my files for the competition. So I managed to find a page talking about open source JavaScript compressors! They're supposed to obfuscate my code, my it unfriendly to be read by humans, while compressing the file size by 40% to 60%. According to this article on zip files, 7-zip can compress down to 76%. If I did that and zipped it, then my total file size should be reduced by 54.4% to 69.6% (the math for that is compressorPercentage + ((1 - compressorPercentage) * (1 - zipCompression)), and that's taking what the compressor has done and using 7-zip to compress what was left).
Comments
Post a Comment