Visit our website www.piratehorizons.com to quickly find download links for the newest versions of our New Horizons mods Beyond New Horizons and Maelstrom New Horizons!
Quick links for Beyond New Horizons
- Download latest version
- Wiki
- FAQ
- Report bugs here
- Bug Tracker on Github
Quick links for Maelstrom
- Download the latest version of Maelstrom
- Download the latest version of ERAS II
- Download the latest version of New Horizons on Maelstrom
Quick links for PotC: New Horizons
- Download latest version
- Wiki
- FAQ
- Report bugs here
Thanks to YOUR votes, GOG.com now sells:
- Sea Dogs
- Sea Dogs: Caribbean Tales
- Sea Dogs: City of Abandoned Ships
Vote now to add Pirates of the Caribbean to the list!
Quick links for AoP2: Gentlemen of Fortune 2
- Downloads and info
- ModDB Profile
- Forums Archive
A Pirate Podcast with Interviews
Music, Comedy and all things Pirate!
- Episode Guide - About - Subscribe -
- Twitter - Facebook - iTunes - Android -
- Youtube - Fill the Coffers -
That's what we all want, and we're trying our best to achieve it.In relation to the question at hand, I would pretty much like build 14 to be stable, and not crash often :urgh
This is exactly why we need more coders either way.Plus, we need to get Build 14 pretty much perfect first. Any bugs in it have the potential to make things worse when porting to Storm 2.8.
In order to do that, we almost certainly need coders to iron out the more complex issues.
That's what we all want, and we're trying our best to achieve it.In relation to the question at hand, I would pretty much like build 14 to be stable, and not crash often :urgh
It's a long process, though, and every time we release a new patch, there's always something that goes wrong for someone.
I'm sure it wouldn't hurt their feelings asking for coders. In my opinion, if kept well organized and near enough synchronized on tasks, then more coders would ease the workload per coder I think. If I was in charge of a group of coders, I would always welcome a new member into the team :nk
The Config manager has "trumph" authority over the board of subject matter experts in prioritizing the one to end list. There has to be a whip cracker that keeps people on task, reassigns tasks if necessary and gives appropriate praise and public acknowledgement for jobs/tasks completed and well done. Bottom line is that coders like leadership.
The Config manager has "trumph" authority over the board of subject matter experts in prioritizing the one to end list. There has to be a whip cracker that keeps people on task, reassigns tasks if necessary and gives appropriate praise and public acknowledgement for jobs/tasks completed and well done. Bottom line is that coders like leadership.
MK, we had similar discussions on organizing back a couple of years ago before we got the source code, I think it might have been just before you joined up here mate. You can read some of our discussions in THIS thread, if you haven't already seen it. We did have other discussions as well, I will look around and see if I can find some more if your interested. I don't think we ever did really reach a final conclusion on anything.
Oh, I'm sure we could achieve that as a joint effort. Even just starting a pinned thread in the Build 14 forum and adding to it as and when would do. :hmmI could write up a list of things to do -in fact I started on that before- but it's a lot of work to even write the to-do list and I don't have a lot of time.