20 Oct 14, 09:56AM
If pause is such a huge problem that almost every solution would be welcomed - how come, no one even tried to check out ACs built-in feature to avoid pauses in matches? It's been a feature since the first AC 1.1
Also, if you want to get involved in the development (and help the next release to get out) - how about you set yourself up for testing? Get a git client and a compiler set and fetch the current master from the repository...
You may find, that there have been a lot of changes since 1.2.0.2 - and there are a lot of protocol changes in the queue, which require a lot of test players to test multiplayer features.
If you don't know, what to test: ask me, I'll point you to an experimental regression test management, where you can check, what others have already tested.
And if this is too easy for you, and you really want to help the game - read yourself into the topic of debian package creation. We've been a year without a proper debian package. If you own a Mac, even better: grab yourself a debugger and get started (if you run out of bugs to catch, just start a thread here, and ask other mac users).
If you're no coder, how about searching for visual errors in maps? How about creating a new set of textures (for example, for all parts of a building)? But you also may want to grab a git client and fetch the latest version - there have been quite a few additions, especially for mappers...
But of course: chatting in the forum about the importance of version numbers is much easier... :)
Also, if you want to get involved in the development (and help the next release to get out) - how about you set yourself up for testing? Get a git client and a compiler set and fetch the current master from the repository...
You may find, that there have been a lot of changes since 1.2.0.2 - and there are a lot of protocol changes in the queue, which require a lot of test players to test multiplayer features.
If you don't know, what to test: ask me, I'll point you to an experimental regression test management, where you can check, what others have already tested.
And if this is too easy for you, and you really want to help the game - read yourself into the topic of debian package creation. We've been a year without a proper debian package. If you own a Mac, even better: grab yourself a debugger and get started (if you run out of bugs to catch, just start a thread here, and ask other mac users).
If you're no coder, how about searching for visual errors in maps? How about creating a new set of textures (for example, for all parts of a building)? But you also may want to grab a git client and fetch the latest version - there have been quite a few additions, especially for mappers...
But of course: chatting in the forum about the importance of version numbers is much easier... :)