Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 2014-12-10 in all areas

  1. I'm sorry if that was how that came across, but all I meant was that if you were no longer going to be able (due to a lack of time) to use those permissions there was no reason for you to have them. It was all about keeping things tidy, and nothing about mistrust. And as leper writes above, there's no war/treating you differently from our side, so if you feel that way it's certainly not intended. What we do want to make clear though is that we will not treat you differently from how we treat everybody else, neither negatively nor positively. The programmers try and review patches as soon as they have time, regardless of who submitted them. We do want to try our best to make sure the code is as good as possible though, and that means that even the programmers who have joined the team sometimes do things separately (whether as a patch or as a GIT branch or however they choose) to make sure bigger changes can be tested/reviewed before being included in the main SVN. Now you may agree with that in theory, but with posts such as the ones in this thread it's hard for us to get that impression of you. In other words, so far your words and your actions seems to speak of an attitude of getting things done and getting them done quickly. And there's certainly good things about that, but when it comes to a project of this size it's practically impossible for one person to fully grasp all the consequences of changing some pieces of code or other. Which is why we want to be a bit more careful than that. True, it might be slower at times, but hopefully it means both higher quality code and quicker development in the long run (if less time has to be spent fixing things later). If you want to do things in a different way and commit things as soon as possible that's something you're free to do in a fork, but please understand that it's not how we want to do things for the main repository.
    4 points
  2. Hello everyone, I'm Alex, new (started on Alpha 17) player on 0 A.D. First I'd like to say that I really love this game, I've been looking for this kind of games for years (I'm 24 years old so I enjoyed all the AoE, AoM etc when I was younger). I just wanted to introduce myself since I've been checking this forum for a few weeks now and really enjoying all the discussion/topics about the game (and I'll try to participate by giving my own ideas for the game in the futur). A big thanks to the development team and all the people that help them, please continue this amazing work. I played only single games until now but now that I'm beating the highest difficulty level against the computer you'll see me soon for multiplayer's games. Sorry about english mistakes. Gauls forever ! Alekusu
    3 points
  3. So you wanted some of the perks of being a team member without any of the obligations? That's not how things work. Also the Wildfire Games Application Form states: Notice the contributions part you stopped doing at some point and never resumed? Your project didn't have much apart from a huge forum post that didn't convey what you wanted to do and huge forum posts about things that might or might not happen have a high tendency to be left unread (or skimmed over and deemed to long). Phrasing your initial post properly instead of demanding something might also have been a better way to help others understand what you wanted to say. Also being intent on forking without even seeking a discussion with the upstream isn't how you're going to get commit access either. No, the first two posts in this topic do not count as seeking discussion. "Whole-world" with only some outside of Europe and America and you posted this on a Tuesday morning (yes, not only you have other obligations apart from just reading this forum), so the chance of anyone having time to read the forum and reply to posts that require knowledge of some things is pretty small. Moderator rights is the wrong term. Priviledge is the word you are looking for (some might say obligation). We are trying to interact positively and closely with modders, but the fluctuations in the CoM and other related issues (read Romulus) might have made us a bit cautious with handing out such priviledges. Your reaction of leaving a short while after also makes that judgement quite right, doesn't it? Because emotions are so easily conveyed across a text-only medium where people have better things to do than wonder whether someone who dropped a few patches and disappeared feels about not getting a response within 10 minutes. You also didn't take care of your other patches, so just adding more to the pile does not really count as helping a lot. You could have forked the git clone and worked there so that others can see your work and we can see how some of the patches might be useful. But you didn't even do that, after neglecting all your patches on trac, and then you come demanding SVN commit access which is an earned priviledge that isn't handed out without any consideration whatsoever. And since then you also didn't even release your changes anywhere and you still wonder why nobody cares about a fork that doesn't give anything back.
    3 points
  4. r16034 adds support for nested repeat tags. See the repeat GUI object documentation on trac. EDIT: Also created #2952 to clean up the summary screen xml.
    2 points
  5. maybe watch this: follow a few rules of thumb as well: -never stop making units -never get population capped (so make houses ahead of time) -make sure you have very little idle units (none is the best) follow those rules and your win-rate vs the AI should go up really, the best thing to do is to invest resources you gather as quickly as possible. don't stockpile resources and you should be set; if you stockpile resources it should be to save up to get something expensive, like transitioning to town phase
    2 points
  6. Looking at the code it should be easy to make the code match another letter. Currently it is hard-coded to use [n], but just specifying what to use in another xml attribute for the repeat tag doesn't sound hard to do.
    1 point
  7. Oh it's not that bad, Aoe3 did it rather well. Still, it's not something too important.
    1 point
  8. Earlier today I pushed some changes to GitHub and also to the live interactable version. The biggest changes are to how the data is parsed... but that happens in the background and is probably not very interesting so I won't go into detail. Of greater interest will be that I've added three more mods that you may activate from the drop-down in the top-right: Amazones by dvangennipDelenda Est by wowgetoffyourcellphone0AD: Ancient Empires by Prodigal SonThe latter two change a lot of the same things and are therefore not compatible with each other. Also, you might encounter problems if you have either one of them and any of the smaller mods active at the same time. I won't prevent you from trying, but... I wouldn't advise it.
    1 point
  9. Ignoring most of your post, but I have to answer to this part: Commits including code you contributed (full listing): r15150, r15677, r15699, r15868. There are some patches on trac that were applied (and are in the above listing), or they did get a review and weren't improved and thus aren't going anywhere, or the ticket was just invalid. Yes, commits can be reverted, but patches can be improved before they are committed and as can be seen you didn't do that. Code contributions (patches) say more than long forum posts and judging from yours your demand for source access, the demand for getting an answer in less than 8 hours, and the above rant some 3 months later is presumptuous at best.
    1 point
  10. Then let's hope someone either corrects you and this works already or someone implements it (Or perhaps rather implement JavaScript being able to create GUI elements as that's probably more useful )
    1 point
×
×
  • Create New...