Jump to content


Community Members
  • Posts

  • Joined

  • Last visited

slipshod's Achievements


Tiro (1/14)



  1. The server code need have nothing to do with the code for the game itself. Its not linked with it, its not aggregated with it - its totally separate. Its not even something you'd distribute (unless you wanted to), as you'd only need it for running 0AD server(s) - the only restriction is that you couldn't run a server for commercial purposes, ie charge money for people to join up for multiplayer games. Is that's what is intended for 0AD? The code that _would_ need to be part of 0AD is the client-side logic that talks to the server, an implementation of which is in Aleph-One, which is GPL. If you still consider it to be unusable due to the non-commercial clause in the server license, well such is life I guess
  2. You may consider adopting the multiplayer metaserver developed by Bungie for Myth, and later open-sourced. The latest version of it can be downloaded here: http://projectmagma.net/downloads/opensource/mythserver_rev67.tar.gz It basically works by allowing clients to join the metaserver, providing them with access to a number of "rooms" in which people can chat, and games can be hosted. Within a room, you can join a game that someone has hosted, and when the host is ready the game begins without having to know any IP addresses etc. When the game's over you're back in a game "lobby", where the game can be changed and restarted, or you can leave to rejoin the main lobby of the room you were in. The server is also capable of storing game results for use in ranking tables etc. Myth multiplayer took place for many years on a site (now gone) called playmyth that ran this code, and now mariusnet.com has taken over the hosting, albeit with separately developed metaserver code. The Marathon Aleph-One open source project also use the mariusnet metaserver, and therefore you can peruse Aleph-One's code for an implementation of how it works from the client-side. Of course 0AD developers might prefer their own solutions, but its worth considering - the Myth metaserver is very stable and works well, why re-invent the wheel etc etc.
  3. Great stuff guys, thankyou! To me the pathfinding is key, so its what I'll concentrate on first. Its great to know that a lot of may be possible through scripts to begin with as well. You've given me enough info to know that the project looks feasible, and hopefully it could benefit 0AD as well, so I've decided to give it a go and see where it takes me.Right now I'm just one person looking at this on his own in limited spare time, so my progress will be necessarily limited. If I can get to a point where I have a working proof-of-concept, hopefully I'll be able to start building a team (there's no way on earth I could do this by myself) and see this through to completion, but first things first I guess.If anyone has any further comments, suggestions or advice it goes without saying that I'd love to hear them.
  4. If anyone's interested, the Myth 2 demo is still freely available (http://tain.totalcod...i-demo-mac-os-x and http://tain.totalcod...i-1-7-2-windows), and will provide a far better illustration of what I'd like to help create than me talking for ages here Even better, plenty of videos exist such as .In terms of changes that'd be required, and please bear in mind that I'm still an absolute n00b when it comes to how 0AD works, first and most obvious would be the need to allow levels that don't require resource gathering/building at all. The units you start with are the units you'd have to work with. Less obvious are more subtle gameplay issues. The implementation of unit pathfinding and combat in Myth is far more detailed, and controllable by the player at a much deeper level, than is possible now in 0AD. Tell a bunch of units in 0AD to move somewhere, and they'll move into a formation and try and hold it while moving to the destination. When a unit gets too far out of sync with the others, it suddenly puts on a burst of blinding speed to get to where its supposed to be. When the bulk of the units arrive at the destination, any units left lagging behind stop where they are. In Myth, units only adopt the formation specified by the player (there are quite a few to choose from) when they reach the destination. In between the starting point and end point, each unit has its own path calculated independantly of the others, and there's no sudden rushing to get somewhere as each unit can only move at its set pace. Each unit will keep moving until it arrives at the destination, even if its long after the others arrive. In 0AD, tell two groups of units to move through each other to a destination on the opposite side of the other group, and they'll meet in the middle, get stuck, then suddenly turn on their burst of speed and scatter around each other. In Myth, the units will more smoothly slide through gaps between other units, or recalculate common-sense paths around the blockage. Also in Myth, the user can click on a destination and drag the mouse to show the direction units should face upon arrival. I haven't found out yet how to do this in 0AD. In 0AD I've seen units chase a fast target (eg a swordsman chasing a deer), and swinging his sword while quite distant from the target unit. In Myth units only use their attacks when in range. I'm sure the more I look the more differences I'll find. Watch the youtube video - you'll see units move smoothly past each other, walk around blockages or wait until a path clears, and units responding precisely to player commands during battle with everything kept under control. If I can summarise, a Myth-like game sees units as individuals, which must obey defined limitations such as their speed, turning rate, attack distances and so on. In comparison, once units given orders as a group in 0AD their seen as members of that group, and rules are "broken" to keep the units in their place in the group or to get past obstacles. The aim of a Myth-like game is to get straight into the nitty-gritty of tactical combat, with the ability to micro-manage units & have them behave logically and predictably being paramount. In 0AD combat is less important than the resource work that precedes it, which is common to many RTS games: click the enemy and the units win or lose on their own, but never mind you can create more units. There's obviously a lot more, such as projectiles units in Myth can pick up that give them special attacks, units that can blow themselves up damaging all others within a radius, units that can heal other units, and so on. There's also the whole multiplayer aspect, the different types of games and scoring methods. For single player there's the ability to script actions of enemy units, and determine win/loss conditions based on seizure of a destination point, or killing a certain enemy unit etc etc. There's the use of the left mouse button to select in 0AD, and the right button to tell selected units to do things. In Myth its left mouse button for both, which is very fast and intuitive, probably stemming from Myth's release for early Macs with their single mouse button. Oh, Myth has flying units as well. After this of course is the huge task of creating the artwork; not only the maps but the new units as well. I'm very aware of how much work creating a Myth-like game would be regardless of the engine used, and to me the first consideration is how difficult it would be to get the basics of gameplay working properly (pathfinding etc). Once thats solved I believe the project will then be feasible, and work on the remaining aspects can be planned and commenced. Btw I don't think replicating Myth is either possible or wise; just making a medieval or fantasy-based 3rd person Real Time Tactics game would be enough to start with. Anyway, thanks for your reply Philip, I'm really impressed not only by the amazing progress you guys have made with 0AD, but also your willingness to consider adding features that might benefit other games using the engine!
  5. Thanks for your reply. By "major piece of coding", do you mean changes to the C++ core of 0 AD, or do you think a Myth-like mod would be possible via Javascript etc? If the former, then it wouldn't be a mod of 0 AD as it'd mean having to make a fork of the game, which would be a major undertaking indeed. Right now I'm trying to decide whether 0 AD is a good starting point or whether I should look for another engine that might prove more suitable. If a fork would be necessary then perhaps 0 AD isn't the ideal engine to use, which would be a real pity there's a lot to love about it, and it seems close to Myth already in much of what it does.
  6. Hi everyone, I'm not sure how many (if any) of you are familiar with the old Bungie game Myth. Basically it had a 3rd person viewpoint with rotating & panning camera, almost identical to 0AD, but there was no resource management. You played through a series of levels, each of which told part of the storyline, and you fought battles with the units you were given. All the emphasis was on detailed battle tactics, managing small numbers of melee, missile and explosive units against AI controlled enemies, which were scripted to either march in patrol, search & attack or defend something. The physics was quite good, with grenades that sometimes bounced or dudded, units that flew apart in pieces when blown up, projectiles that could be accelerated by explosions & sent flying around the landscape, which could be scarred by explosions and blood. There seem to be very few "real time tactics" games like this in existence, and while Myth hasn't entirely died yet its not far off, plus its still not freely available. So I was wondering, would it be possible given the design of 0AD to create a Myth-like mod for this engine?
  • Create New...