MegaGlest Forum
Archives (read only) => Glest Advanced Engine => General discussion => Topic started by: Omega on 8 November 2012, 06:28:15
-
It's no secret that this board has been quiet for a long time. The last official GAE release was December 2010, almost TWO YEARS ago. Even the beta for version 0.4 was last released in October 2011, over a year ago. Since then, there's been hardly any progress with the engine. Besides MoLAos's fork, which is developed on a different path than GAE, there isn't any active development on the fork. There have been no new mods recently, with constellus having been long since abandoned and my own apocalyptic dawn as well. There hasn't been a single commit since September, but even beyond that, commits are few and far between. In other words, the possibility of version 0.4 being released is looking very slim. With the exception of Hailstone, most of the devs no longer frequent the board often, having last visited the board over a month ago. Long story short, the project is looking pretty much dead.
If that is the case, I think we'd be best off to archive the GAE threads and convert the board to full on MegaGlest. There's just no point having another fork lying around if it's never going to be developed.
This topic is meant to ask the community if they agree that the GAE project should be closed down and the rest of the board adapted for MegaGlest use. If this is the case, then the Wiki can also be adapted to be solely for MegaGlest, which would make the development easier and less confusing for future MegaGlest modders. If this proposal passes, I'll personally modify the board and wiki myself. Beyond that of the community, I also would like to hear the GAE devs take on this. I understand that real life comes first, and it can be hard to find time to develop a freeware project. As well, since it's more or less "your" project, it's really the final say of the devs. With that being said, GAE's really looking in limbo, and the MegaGlest project could always use more coders.
So again, if the community is in agreement, we'll:
- Lock and archive the GAE category
- Adapt the board to be better for MegaGlest: move the childboards to be proper categories of their own (MegaGlest logo at the top corner?); set MG devs to universal moderators
- Archive the GAE portions of the wiki, making MegaGlest the dominant topic
Edit 2013-08-06 - Omega: Changed title
Edit 2016-12-31 - filux: Changed title, to all: please don't dare to say project is not dead until the time when source code (with history) will be available to download (again) ... and with at least one fresh commit
-
I don't think this is a good idea. MegaGlest has it's own website.
Your plan might be marginally helpful for MegaGlest in some ways but this is the Glest site for Vanilla Glest as well as the both main forks. It doesn't exist to service the needs of MegaGlest. That's what its own site is for.
You could simply make a MegaGlest section of the wiki or a new wiki just for MegaGlest. Then you don't need to have all the is this feature vanilla mg or gae type stuff with color coded backgrounds.
-
I think this would be a good idea.
Make the top-level categories MG-specific and then put the classic Glest and the GAE boards under child boards
Something like:
Installation and getting started (MG-specific, but you don't need to say that in the title)
General Discussion (MG-specific, but you don't need to say that in the title)
Modding (again MG-specific, without child boards for maps and variations; just put it all in one big bucket; Tools in here too)
(the Glest Advanced Engine fork) (put everything about GAE under here, and put the board name in brackets so its subtly clear its inactive)
(archived forum) (includes all the old Glest boards)
Having too many boards at the top-level, and having too many boards in general, is not making it easier for new people to know where they go to interact with livies
-
This is Pretty sad stuff...
GAE has been on long breaks before has it not? I really hope that is the just the case this time as I fricking loved this game man. 0.4 seemed so close yet we never did quite get there, one last ticket has been haunting trac for months now. My one and only humble request would for that ticket to be closed and then one FINAL version would FINALLY be release (0.4). Just to give it a better ending and maybe inspire some modders to finish old projects (like me) I know I would probably try to fix the crincillin up to a respectable level if this happened. Wasn't Military ( sorry forgot the new name ) also waiting on 0.4 for a release?
I have been working on a new project a at slow but consistant pace for the last couple of weeks, just getting a couple of new models into the game, I'm not sure what the future of the project is but now this thread is making me think about stoping completely.The optimistic side me tells me we should go out and try to actively recruit new coders, but not sure if it's viable/worth doing.
About the forums, I'll stay out of that as I reckon well that should be left completely up to the developers.
-
Your plan might be marginally helpful for MegaGlest in some ways but this is the Glest site for Vanilla Glest as well as the both main forks. It doesn't exist to service the needs of MegaGlest. That's what its own site is for.
True, but vanilla Glest is long since dead; there's no reason it should be used instead of a fork. That's why we archived all the vanilla Glest categories. If GAE has ended up as dead as vanilla Glest, then perhaps it's better to archive it as well. The code isn't going to disappear, but to be honest, there's not much of a reason to mod for GAE, since its audience is shrinking while MegaGlest's is growing. If it's never going to be developed, it's just going to die off. That's why I have to ask "where do we draw the line"? When do we decide that it's just not being developed and we should move to MegaGlest? Months ago, we were complaining about how two separate forks split the community. Perhaps it's better if there's only one?
You could simply make a MegaGlest section of the wiki or a new wiki just for MegaGlest. Then you don't need to have all the is this feature vanilla mg or gae type stuff with color coded backgrounds.
We can, and if this proposal to close up the GAE section fails, we may have to segregate the wiki for the convenience of modders. I initially kept the MG and GAE documentation closely conjoined to ease modding for both engines, but if only one engine is going to be actively used, the joined documentation only serves to confuse.
Make the top-level categories MG-specific and then put the classic Glest and the GAE boards under child boards
I suppose that's an alternative, but it sounds more confusing to me. We'd have childboards for a (potentially?) inactive project. While it shows that the project is smaller than MegaGlest, it's not clear as to GAE's "place". I agree having too many boards in general is detrimental, but keeping all these childboards seems detrimental too. Still, I think it's a good idea to move the old archives to be a child board of an archived "Vanilla Glest" board. In fact, I did that already and it looks much cleaner. If the GAE board is archived, its child boards will remain child boards.
But basically, you'd "lightly" depreciate the GAE boards by implying all other boards are "geared towards" MG without actually archiving the GAE board?
GAE has been on long breaks before has it not? I really hope that is the just the case this time as I fricking loved this game man. 0.4 seemed so close yet we never did quite get there, one last ticket has been haunting trac for months now. My one and only humble request would for that ticket to be closed and then one FINAL version would FINALLY be release (0.4). Just to give it a better ending and maybe inspire some modders to finish old projects (like me) I know I would probably try to fix the crincillin up to a respectable level if this happened. Wasn't Military ( sorry forgot the new name ) also waiting on 0.4 for a release?
I have been working on a new project a at slow but consistant pace for the last couple of weeks, just getting a couple of new models into the game, I'm not sure what the future of the project is but now this thread is making me think about stoping completely.The optimistic side me tells me we should go out and try to actively recruit new coders, but not sure if it's viable/worth doing.
Well, Apocalyptic Dawn was fully abandoned. There was just so many issues (AI didn't use water units correctly, the Glest engine was never a good choice for guns) and I found myself boring with the project. I did secretly start a high fantasy engine-neutral mod near the end of the summer, but didn't get far before university started, and now I'm not sure if I'll ever get time to work on it. Annex for MG is far better than AD ever would be, though. And Constellus never had a proper release at all, did it? The original GAE flagship, Four Path Magitech had a great idea, but its original devs long since abandoned it, leaving the GAE project without much for mods.
Admittedly, the project does seem very close to a release, but it's been in limbo for so long. Recall that the last beta (0.3.93) was released 6 October 2011. I can't believe it's been over a year. However, nearly two years since a stable release and over a year since a beta seems to scream "dead" to me.
About the forums, I'll stay out of that as I reckon well that should be left completely up to the developers.
I don't intend to take any action without word from the current GAE devs (Silnarm, Hailstone, and Yggdrasil). I've already PMed them about this topic.
-
I'm not one of the developers and they are your projests to play with, but maybe it is time to talk about a merge again? After the current release of Megaglest is finished, maybe start porting some of GAE's features that you'd want into Megaglest, if this is doable?
As a user, I'm thinking especially about the crisp graphics that GAE has as well as vanilla Glest did. I never play Megaglest, because the graphics are a bit fuzzy and they make me sick because I'm sensitive to that, and I really would like to play.
Having only one fork is definitely a better use of programmer (and modder, artist, translator) resources, as long as working on it is still fun for everybody!
-
After the current release of Megaglest is finished, maybe start porting some of GAE's features that you'd want into Megaglest, if this is doable?
This is the way forward IMO. Unfortunately because there is no coding standard between the projects this will be difficult.
GAE has some really nice features that should be in MG.
Personally I'm awaiting Molaos' Mandate engine as the next logical extension of GAE.
-
Even if you were to port GAE features over to MegaGlest it wouldn't really be a merger since GAE devs would not likely then start working on MegaGlest. And I think MG already has ported many GAE features over, although obviously not the most significant features.
-
I think the silence speaks for itself.
I'm no longer interested in Glest as a whole. Never played the game much (like more 0ad's and spring's gameplay), but liked working on such a code project. I learned many new things by doing so and that was basically my motivation. I'm still fiddling with the code now and then, but i'm not able to get this project rolling again on my own, especially developing for windows.
So, i'm not sure how to proceed. If you really think converting the Glest board to a MG-only board gives you any big benefit, then seriously go ahead. You won't get an "approval" from me, but a don't care anymore.
-
I think the silence speaks for itself.
I'm no longer interested in Glest as a whole. Never played the game much (like more 0ad's and spring's gameplay), but liked working on such a code project. I learned many new things by doing so and that was basically my motivation. I'm still fiddling with the code now and then, but i'm not able to get this project rolling again on my own, especially developing for windows.
So, i'm not sure how to proceed. If you really think converting the Glest board to a MG-only board gives you any big benefit, then seriously go ahead. You won't get an "approval" from me, but a don't care anymore.
Honestly I was pretty tempted to switch over to 0AD too. They have such superior stuff graphically and they have a far more active community as well as a significant number of contributors.
Sadly they have certain engine limitations that I would have a lot of trouble working around and they just don't have the art assets to compete with Glest stuff right now. All their assets are non european historical and its even harder to manage them due to the increased graphical complexity. Plus it would be quite difficult to modify their gameplay and also the javascript thing turns me off a bit.
But then again their development is just so active that its quite enticing.
-
I haven't given up on GAE or Glest. I've just taken a break to sort out other important things. I think the biggest roadblock has been multiplayer. I've been trying not to work on anything else until that has been sorted at least to a basic level of working. I have a fairly good idea of what is needed to be done. I've been taking a lot of inspiration from how 0ad has done their networking. After that I have many big ideas that can push GAE forward as a base for RTS games.
I'm fine with MegaGlest being in the spotlight. I always imagined GAE as the engine behind the games rather than the game itself. I don't think it's necessary to lock the GAE board though.
-
If this is any consolation; I'm working on a major project that is currently using GAE as its backbone. I do not wish to release details right now, but I hope to have a full community preview by either 1st or 2nd quarter of 2013. This wasn't an issue of development time, but quite frankly I didn't start primary development until April of this year (concept art, prototyping, etc).
By major project I don't mean a hobby mod. That being said GAE is the backbone since it has two key features that will be used in the final product; emanations and shaders (Normal maps). MegaGlest currently does not have those features so it makes it difficult to prototype/test units as they are implemented.
I really would appreciate it if the GAE Wiki portion is kept as it is.
With best regards!
-
Are you modifying code or just art assets and XML?
-
Are you modifying code or just art assets and XML?
All three
-
What code modifications? Anything of serious note that would be applicable to regular GAE or mandate?
-
What code modifications? Anything of serious note that would be applicable to regular GAE or mandate?
I don't have enough information right now to give you precise details, as I said I'll be posting more information in the future. However, I don't believe it will be anything serious of the calibre of Mandate. So far the laundry list includes clean up of visual errors and bugs (terrain tiles), implementation of missing features (such as no submenus for building, unit limitations, etc).
Again it's too early for me to give you a primary list. But I'll be sure to include a list of any main changes in the future. So far based on the needs of this project it's for certain that it will be its own fork.
-
We should try to do a community release instead. Maybe a new beta? It shouldn't be too hard to compile everything.
After that we should try to promote GAE more to get new testers and developers and then if that fails then could close the board.
:-X
-
We should try to do a community release instead. Maybe a new beta? It shouldn't be too hard to compile everything.
After that we should try to promote GAE more to get new testers and developers and then if that fails then could close the board.
:-X
I have to be the one to ask: why should we try and revive a dead (let's call it what it is) project when we have a very much alive project that also could use more developers? The GAE project has some fantastic features, I agree, but do we need a board for it? I can understand making mods for it still (as someone who has firsthand used most of GAE's features at one time or another, they'd pretty fantastic), and the past mods (including my own) aren't going away anytime soon, but what general discussion can we make about GAE? Disregarding this post, we have something that's actually kind of a feature request, a concern about widgets that might never be answered, a thread about an offshoot of the GAE engine, a question about adding a language that has also gone unanswered and that's the last month and a half. The bug reports board serves no purpose if there's no devs to fix bugs (and the last post was early October). Feature requests, likewise, has no purpose with devs to implement features, and was last posted in in late September. That's over two months ago.
Future GAE mods, like all past and present ones, belong in the mods board. GAE's download isn't going to be removed, it'll always be there for future modders and gamers. I'd personally like to see MegaGlest start supporting some of the most important GAE features. Emanations and effects, for example, would be very useful. Shaders would be fantastic for graphics. The cast-spell skill would be incredibly useful for making a healing or buffing unit. Subfactions are actually rather straightforward and make it possible to have impartial stages to a techtree. Loading and unloading has long since been a request by modders. Someone's already working on making levels customizable. The generate command provides an easy way to create resources without having to create a new unit, so Magic's energy source can actually produce energy without needing a size zero unit. GAE's resources have the option to remove the storage cap and manipulate the damage consumable resources deal. GAE allows units to be give a tag which can determine if emanations and upgrades effect them. These are the big changes. There's a lot, but one by one, it's very reasonable to implement MegaGlest alternatives.
Some features, like teleportation, patrol, guard, pets, or multiproduce are less important. It'd be great to see features like them in MegaGlest, but to my knowledge, no mods use them, making them less important. And it's not just about making (formerly?) GAE mods compatible with MegaGlest, it's about giving MegaGlest mods more options. Every mod could benefit from shaders. With subfactions, it's possible for a mod like Annex to upgrade to different stages of technology, with older units being left out of future stages. Maybe it's a choice between being evil and powerful or being good and precise? Emanations make it possible for a building to heal nearby units or a unit to be stronger in packs (but only packs of itself).
I'd personally love to start implementing features like these in MegaGlest, myself, but as a first year student, I don't have the skills yet (perhaps in a year or two).
But do we really need a board for a fork of Glest that might never be further developed?
-
I want to make a post arguing against the idea of another fork but my hypocrisy detector keeps interrupting me with these annoying beeping sounds. No idea why, thing must be broken ::)
I understand the other examples, but what are the unit limitations you refer to?
-
We should try to do a community release instead. Maybe a new beta? It shouldn't be too hard to compile everything.
After that we should try to promote GAE more to get new testers and developers and then if that fails then could close the board.
:-X
I have to be the one to ask: why should we try and revive a dead (let's call it what it is) project when we have a very much alive project that also could use more developers? The GAE project has some fantastic features, I agree, but do we need a board for it? I can understand making mods for it still (as someone who has firsthand used most of GAE's features at one time or another, they'd pretty fantastic), and the past mods (including my own) aren't going away anytime soon, but what general discussion can we make about GAE? Disregarding this post, we have something that's actually kind of a feature request, a concern about widgets that might never be answered, a thread about an offshoot of the GAE engine, a question about adding a language that has also gone unanswered and that's the last month and a half. The bug reports board serves no purpose if there's no devs to fix bugs (and the last post was early October). Feature requests, likewise, has no purpose with devs to implement features, and was last posted in in late September. That's over two months ago.
If you read a certain post in this very thread, hailstone has already said that he is planning to continue mainline GAE development. And clearly people are interested in GAE since it has 2 forks/offshoots. Where would me and Helldiver post if not in the GAE board?
Future GAE mods, like all past and present ones, belong in the mods board. GAE's download isn't going to be removed, it'll always be there for future modders and gamers. I'd personally like to see MegaGlest start supporting some of the most important GAE features. Emanations and effects, for example, would be very useful. Shaders would be fantastic for graphics. The cast-spell skill would be incredibly useful for making a healing or buffing unit. Subfactions are actually rather straightforward and make it possible to have impartial stages to a techtree. Loading and unloading has long since been a request by modders. Someone's already working on making levels customizable. The generate command provides an easy way to create resources without having to create a new unit, so Magic's energy source can actually produce energy without needing a size zero unit. GAE's resources have the option to remove the storage cap and manipulate the damage consumable resources deal. GAE allows units to be give a tag which can determine if emanations and upgrades effect them. These are the big changes. There's a lot, but one by one, it's very reasonable to implement MegaGlest alternatives.
Some features, like teleportation, patrol, guard, pets, or multiproduce are less important. It'd be great to see features like them in MegaGlest, but to my knowledge, no mods use them, making them less important. And it's not just about making (formerly?) GAE mods compatible with MegaGlest, it's about giving MegaGlest mods more options. Every mod could benefit from shaders. With subfactions, it's possible for a mod like Annex to upgrade to different stages of technology, with older units being left out of future stages. Maybe it's a choice between being evil and powerful or being good and precise? Emanations make it possible for a building to heal nearby units or a unit to be stronger in packs (but only packs of itself).
I'd personally love to start implementing features like these in MegaGlest, myself, but as a first year student, I don't have the skills yet (perhaps in a year or two).
But do we really need a board for a fork of Glest that might never be further developed?
Its obvious what the benefits to MegaGlest would be if people didn't have other options as to where to contribute modding and coding talent, although most people go to 0AD or Spring these days, but that's not a valid argument for closing down the GAE board.
And MegaGlest would have been useless for me personally, if I had not seen the GAE board and its feature list I wouldn't have been able to get anywhere and would probably be somewhere like 0AD now. MegaGlest is terrible for single player projects with its entire dev focus on multiplayer, the probably need to dig into the network code to not break the game, which is not necessary with GAE and its immense lack of features that GAE has which you so helpfully listed for us.
Just give up this closing the GAE forum thing. Its not happening.
-
I don't think the GAE board should be done away with. The help I've received from the folks that have answered my questions has been invaluable since some stuff is different in GAE than in MG (for example; building progression animation).
Additionally it's been very evident that the MG project and even GAE have their own goals. I'm avoiding engine bloating. This means that a lot of the features in MG will be done away with or removed in the version of Glest I will use.
A lot of features that I've taken for granted in a game like Age of Empires Online are missing or have outright been disabled for no apparent reason. Unit limitation for example, was removed in GAE for no reason other than the author/s of GAE felt like it (at least that's what I've come to understand).
Conversely why hasn't the MG team ported in Normal map and Shader support? Is there some huge difference between GAE and MG that prevents it? Also, why no emanations in MG?
For those reasons it has become apparent that I will have to take the GAE source or MG source and modify it to have the features specific to my needs. However as I explained in a message to tomreyn; it would become it's own seperate non-Glest community fork available seperately for free on a different website/location. The Glest community will be free to use it in GAE/MG if they wish however.
Currently on our project, I do not have a dedicated programmer. It doesn't make sense to bring one on since I'm still in the arts and assets phase and GAE Beta 3 has worked perfectly for prototyping and testing. In the future I'd be more than willing to work with any members of the community, it's just that right now it's too early for me.
-
Disregarding this post, we have something that's actually kind of a feature request, a concern about widgets that might never be answered.
Using me as an example aye?
Well just sayin', that thread was really just to see if I was wrong (which I very well could be, I know I came off as a bit angry though). I know people such as yourself or wciow would know more about widgets than me. Plus hailstone's still around, he might of known something about it.
I may of been hopeful, but I'm still kinda glad I have somewhere to post... Even if it is just an angry concern about widgets that might never be answered.
-
Hey, as much as I would hate to see GAE and it's wonderful features (did you hear that Softcoder?) die, I'll stand behind the decision if it finally unites our relatively divided community.
Our division was one of the reasons that people were not too fond of our game, they were never too sure what to do to get it (and once they did, we had nothing too special to keep them here).
Speaking of that, we need a gimmick, something to attract people to our community. Spring has an extensive modding community, and 0AD has visuals. What do we have? We have a crappy story that we're moving farther and farther away from as time goes on. What can MG add to the table that hasn't been done before?
-
MG has hewn quite closely to being a poor man's Warcraft. Many announced projects seem to be the same kinds of custom maps that were popular from Warcraft 3 and Starcraft like Tower Defense, MOBA (BattleGlest for instance), and so forth.
The goal of free or indie games has to be to provide some value which cannot be found in major commercial games because they cannot compete on story, art, or performance, and certainly not on multiplayer. Battle.net rules all.
MegaGlest's primary strengths are that it is free, it piggybacked on the Glest name, and that it runs on platforms that commercial products choose not to support because it is not cost efficient.
However Linux users can get Windows for gaming and Wine also plus Steam for Linux and Desura stuff so most of those reasons no longer suffice.
Its only current strength therefore is its free nature but 0 AD and many other games which provide no cost and also improve in many aspects like graphics and historical accuracy.
-
The goal of free or indie games has to be to provide some value which cannot be found in major commercial games because they cannot compete on story, art, or performance, and certainly not on multiplayer. Battle.net rules all.
This. If you've already got a copy of Warcraft 3 (and most people who would be interested in playing Glest probably already do), why play Glest unless you're just an avid supporter of FOSS? Better art, better story (in that it has one), more varied gameplay, more balancing, huge multiplayer community, etc. We indie enthusiasts can't out-produce professional full-time developers, but we're free to take risks and explore whatever crazy innovation suits our fancy. There is no reason I can see for trying to fit the mold of a standard Age Of Xcraft game unless that's just what you really enjoy doing.
-
To be honest, I preferred Spring's multiplayer client to Battle.net. Actually, Spring's multiplayer is the best multiplayer system that I've ever found.
-
The goal of free or indie games has to be to provide some value which cannot be found in major commercial games because they cannot compete on story, art, or performance, and certainly not on multiplayer. Battle.net rules all.
This. If you've already got a copy of Warcraft 3 (and most people who would be interested in playing Glest probably already do), why play Glest unless you're just an avid supporter of FOSS? Better art, better story (in that it has one), more varied gameplay, more balancing, huge multiplayer community, etc. We indie enthusiasts can't out-produce professional full-time developers, but we're free to take risks and explore whatever crazy innovation suits our fancy. There is no reason I can see for trying to fit the mold of a standard Age Of Xcraft game unless that's just what you really enjoy doing.
But the way to do that is modability... which is limited in Megaglest trying be a game first and not an Engine.
Not saying MegaGlest isn't modable. Just, if a feauture doesn't get implemented because it "doesn't fit MegaGlest". Then you're doing it wrong.
Really to allow greater modability ( In the sense of entirely different games), we need features like custom AIs and stuff - Not just a few varribles changed in xml. Perferably written in Lua.
Offtopic Edit: Zoy, please don't tell me you're a brony now haha.
-
The goal of free or indie games has to be to provide some value which cannot be found in major commercial games because they cannot compete on story, art, or performance, and certainly not on multiplayer. Battle.net rules all.
This. If you've already got a copy of Warcraft 3 (and most people who would be interested in playing Glest probably already do), why play Glest unless you're just an avid supporter of FOSS? Better art, better story (in that it has one), more varied gameplay, more balancing, huge multiplayer community, etc. We indie enthusiasts can't out-produce professional full-time developers, but we're free to take risks and explore whatever crazy innovation suits our fancy. There is no reason I can see for trying to fit the mold of a standard Age Of Xcraft game unless that's just what you really enjoy doing.
But the way to do that is modability... which is limited in Megaglest trying be a game first and not an Engine.
Not saying MegaGlest isn't modable. Just, if a feauture doesn't get implemented because it "doesn't fit MegaGlest". Then you're doing it wrong.
Really to allow greater modability ( In the sense of entirely different games), we need features like custom AIs and stuff - Not just a few varribles changed in xml. Perferably written in Lua.
Yes, it's why Spring became so popular! I remember when the "Lua Boom" happened, when Spring got full support for LUA addons. After that day, Spring became what it is today! You know, it barely resembles Total Annihilation anymore. If we increased our modability, we could increase the size of our fanbase. So, devs, what are you going to do next?
Offtopic Edit: Zoy, please don't tell me you're a brony now haha.
Would it be a problem if I was? ;)
-
It might be a good idea to implement a system like 0AD where gameplay is done in the embedded JS engine or something. That would allow significant modifications without having to compile.
Having to compile limits all Glest engines in the gameplay department. Offloading it all to XML like I am is certainly no more than a stop gap and the current Lua implementation isn't that much better.
-
The goal of free or indie games has to be to provide some value which cannot be found in major commercial games because they cannot compete on story, art, or performance, and certainly not on multiplayer. Battle.net rules all.
This. If you've already got a copy of Warcraft 3 (and most people who would be interested in playing Glest probably already do), why play Glest unless you're just an avid supporter of FOSS? Better art, better story (in that it has one), more varied gameplay, more balancing, huge multiplayer community, etc. We indie enthusiasts can't out-produce professional full-time developers, but we're free to take risks and explore whatever crazy innovation suits our fancy. There is no reason I can see for trying to fit the mold of a standard Age Of Xcraft game unless that's just what you really enjoy doing.
I wouldn't bundle Glest with what most now come to know as "Indie". Glest GNU/GPL liscense makes it difficult for an Indie dev to monetize on it to at least return the investment put in to both polish it and make a viable commercial game out of it. You can still do it, but your options are limited. Currently the only use for Glest is for the at-home enthusiast, hobbyist, or as a prototyping tool.
Without being able to put your Indie Glest driven title on Steam, it cuts what oppertunities of distribution you have. Making a polished game that looks proffesional and not just another at-home hobby project takes time and money. Additionally Glest as it is (MegaGlest or GAE) just isn't polished enough and in a state for a viable commercial release. However, I believe with a bit of investment it can be. Unfortunately I don't know of any serious indie team that would want to use Glest, not because of what it can or can't do, but because of the GPL/GNU provisions.
I really wish the team behind Glest would have used a liscense similar to Unity (provisions for Indie but, a per-seat fee for legal entities/developers with more than $100k a year income). That way the at home enthusiasts could still make their mods as they've always been and indie devs could use it as a foundation. Funds taken in from commercial sales could go to improving the foundation source. Additionally by it not being GPL/GNU (or using a liscence that doesn't include source) it would encourage investment in the engine.
Why did I choose Glest over Unity/UDK, etc? Neither of those engines comes with a solid RTS api. Well they sort of do, but all of them are in research phases, require significant programmer time to get them fully implemented, and have high costs (not including programming time and research). Glest allows a non-programmer like me to easily "plug-and-play" the data of my game. Sure I still have to mess with the source, but nothing compared to the barebones Unity or UDK approach.
The problem with the GPL/GNU is that you have to include the source with your distribution. That means that any third party middleware you plug into the source code (or link libraries to) would cancel/conflict with the liscense. That means; no Steamworks (for steam distribution), no scaleform (for UIs), no flash (for UIs), DRM wrapper/handler and so on. Online digital distributors such as Steam, Direct2Drive/Gamefly, Gamer's Gate require a DRM setup so you can set up their authenticator systems. As far as I know none of these allow GPL/GNU covered engines or any such liscense that requires providing the source code.
That severely limits what can be done with an engine :( As I explained in another post; proffesional grade work costs a lot. Even recovering the costs just to break even can be difficult when you can only self-publish.
I have no problem donating to the Glest community to get the features I specifically want or need. The problem is when I add those costs on top of development costs it can severely hurt my enthusiasm particularly since I won't be able to distribute on Steam.
-
A pay what you want scheme with quality assets could get you some pretty decent money although even MegaGlest doesn't have the multiplayer to support a community of any real size.
You could arguably also make your money on multiplayer if you implemented a solid multiplayer service. AFAIK the GPL applies to the code, you can charge for assets and multiplayer and such without conflicting with the license.
-
I had no trouble getting the commit bit on GAE and features I coded for MG into MG either. I mean, there's no hurdle to contributing to either or both projects, and MG has never - in my actual experience - been anti-feature.
I had no trouble getting code in to support Mr War's mods even though sci-fi is miles from MG's "story line".
What I think people misinterpret is that MG want you to explain how your feature is complete and water-tight before it gets committed, which we can thank them for. If you add water buildings, they'll want to know what the AI does with them...
As an observation GAE was more open to untested incomplete submissions, which is totally cool and totally what they were about facilitating.
But we can talk about big plans and mull why MG isn't cool enough to be mainstream, but it really bugs me how the less you can yourself create the more dismissive you are of the excellent, painstaking, never-ending work people like Softcoder and Silnarm and co have put in.
-
Open source projects never die.
GAE was sleeping.
-
Does than mean your starting up GAE development?
-
It does indeed.
-
It does indeed.
BOOM!
http://youtu.be/vqVNLd_7Mqo
-
AND THE PEASANTS REJOICE!
Depending on your progress, I may need to take glest up again.
Lovely to see you aswell. :|
-
This is excellent news! :D
Haven't been active on these forums for the last year or so but I'll have to get back to modding now. :swordman:
-
I may return as well..
Glad to see you about again Silnarm! ;D
-
Yeah, a big welcome back party.
Seems to be a good time to get a bit more active. We should somehow sort out how to proceed... Particularly, what was the difference between master and the 0.4.x branch and why did we need that?
-
Depending on your progress, I may need to take glest up again.
I'll be spending what time I can on it, but that will probably not be much so progress is not likely to come fast. It is was it is.
... Particularly, what was the difference between master and the 0.4.x branch and why did we need that?
I think the idea was to keep 0.4.x for fixage only while new work could go on on master, probably could be merged up, will peruse the logs sometime this week and make sure nothing to dangerous is in there.
-
Depending on your progress, I may need to take glest up again.
I'll be spending what time I can on it, but that will probably not be much so progress is not likely to come fast. It is was it is.
... Particularly, what was the difference between master and the 0.4.x branch and why did we need that?
I think the idea was to keep 0.4.x for fixage only while new work could go on on master, probably could be merged up, will peruse the logs sometime this week and make sure nothing to dangerous is in there.
What stuff have you thought about working on? I think Hailstone or someone wanted to do multiplayer. Any other major changes planned?
-
What stuff have you thought about working on? I think Hailstone or someone wanted to do multiplayer. Any other major changes planned?
Graphics (particle systems & shaders + modernising GL use).
AI (interface to Lua, reimplement current AI in Lua, and then start teaching it to use transports, boats, teleporting units etc)
As was my want previously, I am likely to 'wander' a bit ;)
-
Graphics (particle systems & shaders + modernising GL use).
YES. :thumbup: :D :D :D
-
What stuff have you thought about working on? I think Hailstone or someone wanted to do multiplayer. Any other major changes planned?
Graphics (particle systems & shaders + modernising GL use).
AI (interface to Lua, reimplement current AI in Lua, and then start teaching it to use transports, boats, teleporting units etc)
As was my want previously, I am likely to 'wander' a bit ;)
A Lua AI would certainly be interesting. I think 0AD does AI in JS which is similar since they are scripting languages, and I think Spring uses tons of Lua.
-
Yes Lua AI would get rid of some problems. Look at MG, while Softcoder has made the AI a little more customizable to the user via XML it still has major problems with anything slightly different from original Glest designs.
So will this entail having an AI script continuously running in the background?
-
Yes Lua AI would get rid of some problems. Look at MG, while Softcoder has made the AI a little more customizable to the user via XML it still has major problems with anything slightly different from original Glest designs.
So will this entail having an AI script continuously running in the background?
Damn, now I kinda wanna wait to do any work on my AI till we see what Silnarm does. I will still manage the current AI for Majesty-likes but probably wait for any other kind.
-
Welcome back Silnarm. I've done a rewrite of the networking stuff to use turn based lock-step networking which is working for the local interface but it needs some more work for the server/client interfaces. I'm not sure if my commits have been pushed to the server yet.
-
So will this entail having an AI script continuously running in the background?
Yep, each AI running in its own 'Lua state'.
Welcome back Silnarm. I've done a rewrite of the networking stuff to use turn based lock-step networking which is working for the local interface but it needs some more work for the server/client interfaces. I'm not sure if my commits have been pushed to the server yet.
Sounds most interesting, this rewrite replaces/heavily-changes the Commander class and command queuing system I assume? Would love to take a look, get it pushed, may need to reset the remote (as Frank mentions here) or clone from the new repository and patch serial, if you're still on the old repo.
-
Sounds most interesting, this rewrite replaces/heavily-changes the Commander class and command queuing system I assume?
It doesn't really change the assigning commands. It's more about changing the network communication so that commands are executed at the same time. For example each turn could be about 1/3 of a second. These are sent to the server and broadcasted to all clients (this could be multithreaded later). On the third turn we hope every player has the 1st turn so every player executes that turn at roughly the same time. It introduces a slight delay that should be disguised by animation/sounds but makes sure everyone is together. The turn length could be adjusted depending on rendering and network speed. It's based off of 0ad which was based off http://www.gamasutra.com/view/feature/3094/1500_archers_on_a_288_network_.php