So I finally have some free time to get back into GearHead development. The first order of business will be to get the plot/quest system back up and running. After that, whatever changes will be made to the game system.
Please fill me in on anything that's happened since I've been gone (i.e., employed). Also, I should probably start incorporating patches into the main branch. Is there currently a definitive version of GHAR?
Welcome back, in that case. Hope you have been enjoying your new job so far, by the way.
Not much has happened AFAIK, besides forum activity and non-activity (the mysterious disappearance of Peridot being a highlight to some of us
Yes, what Deamonward said. I myself got around to cloning Peridot's repository and beginning to make my own contributions, mostly content and an attempt at a GHAR/Lua stdlib, but I stopped soon after for various reasons not excluding 'lack idea of what exactly is needed', and 'lazyness'.
Besides a working plot system, I for one think what GHAR needs most is clear vision and direction. Not in the fluffy business-talk sense; let me elaborate: there are a number of good souls around here who like the idea of contributing code-wise to GH, but often really don't know where to start or go from there. Sometimes not so, yes; some take initiative better than others. But anyway, clear designs and ideas are needed. You seem to be a busy guy, JH, and we'd like to help out a bit. But we are in disarray (code/design-wise). At least that's how I feel. Hopefully it's not just my Stupidô and lack of sleep currently speaking.
For example, you wish to improve the damage/armor/mecha engineering systems, which I think is a great idea. Please lead a design discussion on this, and let's work out some details. Or you just work out details on your own and others comment as you go along. Or someone ingeniously develops the bulk of the ideas as you approve and disprove parts of it. Or anything in between. In every case, it would be good to have some place to get a reliable, final record of "how this shit should be done", whether I/whoever is trying to actually do "that shit" in Pascal/Lua/arena/Gimp (hah), or just updating the wiki on a new system (the wiki is known for its crimes against information accuracy).
Point is, we generally need you in order to contribute. Need you to keep things clear and decide what would and should generally work for GH and what not. Because 'us guys' can keep on and on ranting and brainstorming so many good, bad and ugly ideas and even get some prototypical experiments
(or patches) up and running, but we would still be unsure whether they are good ideas or bad, whether to refine them further any time soon, or how to go about them etc. And without you to dictate on the matter, some of us will forever keep on wondering how exactly to interpret the concept of beam shields. And stuff like that.
So yeah, mainly just asking for more of your feedback and decisions on some of the ideas/conundrums that float around the forum. And if you can, structure design discussions from which others can begin working to add, change or improve parts of GHAR. And if you can't lead design, whether for lack of any clue about what should be done or for lack of time or for any other reason, let us know. Of course, I'm not asking you to scrutinize every suggestion that someone makes, but at least have a peek and share your thoughts more often. And of course, I'm not saying that we should get a formal development cycle running (we're all GH hobbyists, no?), just that a hint of development leadership might do a whole lot of good.