FA+
Shop
EoYG Update #2
10 years ago
Baron: "Ladies, I shall require your assistance."
Lady 1: "Of Course!"
Lady 2: "Anything!"
Lady 3: " Just tell us what to do!"
Baron: "Kindly, be so good, as to remove your knickers."
Lady 1: "Of Course!"
Lady 2: "Anything!"
Lady 3: " Just tell us what to do!"
Baron: "Kindly, be so good, as to remove your knickers."
Bi-weekly updates... go figure.
TL:DR Version
Game: Is progressing and I'm working on a prototype magic system to be included in the alpha. General numbers will be used. More in-depth details will be given later.
Maya: Autodesk financing never got back to me, but *Knocks on wooden table* I should be able to buy Maya by the end of the month WITHOUT killing my savings.
30 Pieces: Been sketching finally and taking a bit of time off from working on the shading network. Not happy with anything yet enough to sketch, but I might start uploading what I've been doing soon just to get feedback.
Website Update: Found a few... interesting... options? But nothing with all the stuff I'm looking for. Once Maya is mine, I might fork up $19/mo to adobe for a few months just to update the site. I'm not 100% convinced it's worth it, but it doesn't seem like that bad of an option at the moment....
Long versions
The game is coming together in bits and pieces. The base "bricks" are made and destructable, but I want them to regulate mana income and a few other things. The destructable brick code should work well for the runes and waystones. The thing I'm trying to figure out is how to update a few behind the scenes stats on creation and on destruction though while having a bit of randomness and some unpredictability as more and more runes get destroyed. The general concept is that the waystones provide you mana and chaos while the runes provide protection for the waystones and stability. Both can also provide elemental filtering/imbuing which is a separate layer that I do NOT plan to tackle just yet. Been mulling over the math of these systems and I think I've finally got something, somewhat worked out. Gonna try implementing it over the next week or so.
Been mulling over my paycheck as well over the last week or two and... I think I can actually purchase Maya without any major issues. I still plan to wait till at least October just to give myself a little bit of a cushion because of future unknowns, but it's now looking very, very good though. As soon as it's bought, I will be able to work fully in the program for games and animations without the worry of Autodesk coming out of the blue one day to slap me with a suit or fine or some other crap for using an "educational" version for profit. At this point however, I've pretty much given up on their Financing division on EVER getting back to me and their website's support section seems woefully missing any actual contact information for their financial division.
Sketches have been... coming.. but I'm still trying to get out of the "burned earth" methods I had been doing. Not happy with any of it, but I am starting to save it now and then. It's mostly just trying to doodle out random ideas here and there, but it keeps hitting odd bits here and there. It's not all bad, just annoying as it was before. Still working on that board game here and there and some of the assets are coming together for it. I am still fiddling with maya as well with some 3D doodles as well. A shading network that I've been prototyping out for the game however is backburnered for the moment due to me trying to relearn too much at once and hitting a confusing catch 22 wall of cyclic thinking. For right now, I'm refocusing on modeling first then going toward basic texturing, then rigging, then shading networks/scripting. I might start posting some of the better looking 3D doodles. There's still rust on the Maya gears in my head, but they are turning once again.
Found a good many bits out there from Kompozer to Bluefish and there does seem to be a lot of promising stuff out there. The biggest issues I seem to keep coming across is that most of the programs don't have WYSIWYG page viewing and/or their support was dropped a few years ago and are no longer being updated. I wouldn't worry about that second issue soo much if it wasn't for the fairly drastic overhauls happening to web browsers. Between Firefox... well... actually firefox seems to be one of the only ones that hasn't changed in any significant ways. It's still a memory hog of a browser that some people program rather hoity toity websites for (We've probably all seen the occasional site that comes up with "This site requires firefox to view"). Chrome appears to have had quite a bit of backend updates, including one that should reduce it's memory footprint by ALOT. Internet Explorer appears to be dead with Microsoft Edge being it's replacement. Opera, an old favored browser of mine, seems to be spinning in place, trying to add new features every update while screwing up what used to work flawlessly. Then there's the ol' spinning wheel Safari which, despite Apple trying to patch their leaky ship, is still as full of security holes and flaws as it was 3 years ago when I graduated and still supposedly has issues with some CSS and JS enabled sites as well as issues with newer stuff like HTML5 and CSS2. Now, take all those issues, multiply them by the various versions of the Browsers people are running, multiply that again by the mobile market browsers out there and then try to figure out how well something that hasn't been updated in about 2+ years will fare. Needless to say, that $19 per month Adobe single program subscription doesn't look that bad for a couple of months while I update my website. I mean, it's still looks like a sham of the highest order, but, it's not something I'm going to rule completely out anymore. At least, for the peace of mind that what I want to get working should work across the many, many, many browsers out there. I might just drop this goal for the moment due to it going from being complicated, but fairly straightforward to a knotted spaghetti mountain that could potentially rival Denali in height that needs to be unwound before anything can be done with it (topical humor ftw maybe? Eh. I'll still probably call it Mt McKinley. It's what I've known it as for 27 years and they can't change that). Perhaps that board game can fill this slot if things get to that....
Finally, wow. I actually have been updating fairly regularly? The journals at least anyway. The main submission gallery hasn't seen any direct action in a bit over a year. At least these seem to help keep me on track. When I look at what I've been working on, I don't see much progress, but through these journals, well, there does seem to be a bit of forward-moving traction finally. It's kinda weird to see the progress through journals, but I can't complain. I actually feel like I've been accomplishing stuff. Not just getting through things either, but actual accomplishment. Even from unfinished things, these journals are odd retrospectives on what I've been doing and seeing how things are going. Just gonna have to see where these journeys will take me.
TL:DR Version
Game: Is progressing and I'm working on a prototype magic system to be included in the alpha. General numbers will be used. More in-depth details will be given later.
Maya: Autodesk financing never got back to me, but *Knocks on wooden table* I should be able to buy Maya by the end of the month WITHOUT killing my savings.
30 Pieces: Been sketching finally and taking a bit of time off from working on the shading network. Not happy with anything yet enough to sketch, but I might start uploading what I've been doing soon just to get feedback.
Website Update: Found a few... interesting... options? But nothing with all the stuff I'm looking for. Once Maya is mine, I might fork up $19/mo to adobe for a few months just to update the site. I'm not 100% convinced it's worth it, but it doesn't seem like that bad of an option at the moment....
Long versions
The game is coming together in bits and pieces. The base "bricks" are made and destructable, but I want them to regulate mana income and a few other things. The destructable brick code should work well for the runes and waystones. The thing I'm trying to figure out is how to update a few behind the scenes stats on creation and on destruction though while having a bit of randomness and some unpredictability as more and more runes get destroyed. The general concept is that the waystones provide you mana and chaos while the runes provide protection for the waystones and stability. Both can also provide elemental filtering/imbuing which is a separate layer that I do NOT plan to tackle just yet. Been mulling over the math of these systems and I think I've finally got something, somewhat worked out. Gonna try implementing it over the next week or so.
Been mulling over my paycheck as well over the last week or two and... I think I can actually purchase Maya without any major issues. I still plan to wait till at least October just to give myself a little bit of a cushion because of future unknowns, but it's now looking very, very good though. As soon as it's bought, I will be able to work fully in the program for games and animations without the worry of Autodesk coming out of the blue one day to slap me with a suit or fine or some other crap for using an "educational" version for profit. At this point however, I've pretty much given up on their Financing division on EVER getting back to me and their website's support section seems woefully missing any actual contact information for their financial division.
Sketches have been... coming.. but I'm still trying to get out of the "burned earth" methods I had been doing. Not happy with any of it, but I am starting to save it now and then. It's mostly just trying to doodle out random ideas here and there, but it keeps hitting odd bits here and there. It's not all bad, just annoying as it was before. Still working on that board game here and there and some of the assets are coming together for it. I am still fiddling with maya as well with some 3D doodles as well. A shading network that I've been prototyping out for the game however is backburnered for the moment due to me trying to relearn too much at once and hitting a confusing catch 22 wall of cyclic thinking. For right now, I'm refocusing on modeling first then going toward basic texturing, then rigging, then shading networks/scripting. I might start posting some of the better looking 3D doodles. There's still rust on the Maya gears in my head, but they are turning once again.
Found a good many bits out there from Kompozer to Bluefish and there does seem to be a lot of promising stuff out there. The biggest issues I seem to keep coming across is that most of the programs don't have WYSIWYG page viewing and/or their support was dropped a few years ago and are no longer being updated. I wouldn't worry about that second issue soo much if it wasn't for the fairly drastic overhauls happening to web browsers. Between Firefox... well... actually firefox seems to be one of the only ones that hasn't changed in any significant ways. It's still a memory hog of a browser that some people program rather hoity toity websites for (We've probably all seen the occasional site that comes up with "This site requires firefox to view"). Chrome appears to have had quite a bit of backend updates, including one that should reduce it's memory footprint by ALOT. Internet Explorer appears to be dead with Microsoft Edge being it's replacement. Opera, an old favored browser of mine, seems to be spinning in place, trying to add new features every update while screwing up what used to work flawlessly. Then there's the ol' spinning wheel Safari which, despite Apple trying to patch their leaky ship, is still as full of security holes and flaws as it was 3 years ago when I graduated and still supposedly has issues with some CSS and JS enabled sites as well as issues with newer stuff like HTML5 and CSS2. Now, take all those issues, multiply them by the various versions of the Browsers people are running, multiply that again by the mobile market browsers out there and then try to figure out how well something that hasn't been updated in about 2+ years will fare. Needless to say, that $19 per month Adobe single program subscription doesn't look that bad for a couple of months while I update my website. I mean, it's still looks like a sham of the highest order, but, it's not something I'm going to rule completely out anymore. At least, for the peace of mind that what I want to get working should work across the many, many, many browsers out there. I might just drop this goal for the moment due to it going from being complicated, but fairly straightforward to a knotted spaghetti mountain that could potentially rival Denali in height that needs to be unwound before anything can be done with it (topical humor ftw maybe? Eh. I'll still probably call it Mt McKinley. It's what I've known it as for 27 years and they can't change that). Perhaps that board game can fill this slot if things get to that....
Finally, wow. I actually have been updating fairly regularly? The journals at least anyway. The main submission gallery hasn't seen any direct action in a bit over a year. At least these seem to help keep me on track. When I look at what I've been working on, I don't see much progress, but through these journals, well, there does seem to be a bit of forward-moving traction finally. It's kinda weird to see the progress through journals, but I can't complain. I actually feel like I've been accomplishing stuff. Not just getting through things either, but actual accomplishment. Even from unfinished things, these journals are odd retrospectives on what I've been doing and seeing how things are going. Just gonna have to see where these journeys will take me.
