Vote on the prioritisation of modulesProgress is happening in many fronts. After we migrate, progress will happen in 1 front at a time however. We decided with the Wizard that the ultra-small 2-man design&development team can most efficiently work by modularising the developments, and then concentrating on one at a time, subcontracting some, and making others subgame-like joint projects (everyone already knows that most subgames are 3rd party developments that access the game via API and other methods).
The project to get the game core in order started 2 months ago and 3 months are ahead. I want to emphasize that the team is me who is not coding, and one committed part-time Wizard. And the productivity is so high that there are no plans to add more people to either design or development core team, rather define the interfaces how others can make content in the game. Also marketing and administration side require manpower soon.
But as for the vote, the following modules have been proposed and they are largely independent of each other, so that they can be implemented in any order. The modules are only for the game features, they are not the larger project goals (marketing etc).
We are talking about the situation after migration, so the starting point is that the game status is in Ultima DB, the access is via authentication, and Ultima is used for initialising the transactions. List them in order with the first being most urgent, and feel free to leave out stuff that is not in the top of the stack. If you add new modules, don't list very small things, they will be developed/fixed in parallel anyway:
Agora Marketplace - Matching Exchange System for Items & Lots (if we assume that otherwise the full-fledged matching is not active, and trades can be done directly via commands)
Duty Paid - Shop for every possible item to be created from IC (otherwise the creation will happen via admin commands upon char request, with most items just not being created except by admins themselves)
Graphical Building Designer - Build with Voxels, costs and data are entered automatically (otherwise the building will be designed in spreadsheet and translated to a DB entry and imported with a command)
Building View - View and Edit Building Data (otherwise the /BLDG tab will stay in GoogleDB even if the rest migrates, because of usability)
Halls of Fame - See the Best Performers in Multiple Challenges (otherwise such listings are not visible, cf. /CHAR tab)
Health Challenge - To make individual drinking/health choices possible (otherwise drinking will be some script with very little control by the char, as it has been now)
Game Event History / Transaction History - Handy view to see what has happened in your account (compared to no such possibility)
More Realistic Building Payout Script w/choices (otherwise the scripts stays exploitable, and you have no choices over the use of your buildings)
Business - Building - NPC interaction (this needs to be enabled to get back the economic subgames that were in use in 1550-1599 <- note in our history of almost a year, they were in use for 1.5 months only
)
API (includes all tools for programmers to make stuff that interacts with the game)
New Player Registration + Tutorial (else there is none, meaning no new players!)
Automated deposits/withdrawals (if not, current system will continue with manual communication and entries)
Logistics script to calculate traffic and desirability of lots (a great addition to value the rentals based on "actual" traffic flows determined by where people live and walk and desire to eat)
RESTA subgame and making eating and drinking happen in there (a business with actual perishable foods, location and marketing matters)
Countryside with Counties, Duchies, new Towns, RoadsForeign trade and inter-town trade subgame (getting rid of IC happens here probably and m will reign)
Other "core" economic subgamesChapelry view new layer "bird's eye" shows the "satellite" image of the area (else only the 3 different block image layers are available)
Chapelry view new layer "dissect" shows the view at the chosen elevation (3D building db is needed here)
3D first-person street view3D bird's eye view