Thargoid wrote:Along similar lines, is anything planned to capitalise on the previous one (player --> player.ship)? I recall a lot of talk and discussion about that separation allowing distinction between the player and their ship (to allow multi-ship operation or similar) but as of now it's just been a reclassification of a few JS functions.
This might really surprise you, but the equipment & missiles changes in trunk are exactly that: stuff that was only possible to do with player & that was moved to player.ship is now possible to do with
any ship.
As far as roadmaps go, I can give you the general outline, at least from my perspective: we're trying to remove as many bugs as reasonably possible, improve the interface a bit and - perhaps the single most important thing as far as the next stable release is concerned - improve the scripting side of things.
The last bit covers a multitude of sins - I don't really have a complete list of things being changed for 1.74 (we've had more than 500 commits since 1.73.4) but here are some highlights of what's happening: we're completing the events available for scripts, we're finishing off the legacy ->js migration (e.g. at last we have a system.addShip() function to run in parallel with the _legacy ones - it's more flexible, and easier to use, and should be bugfixed any moment now), introducing a vastly improved mission screen handling, plugging scripting omissions - more things are scriptable now, and more info is available to scripts (eg some of the new ship & player.ship properties: missiles, equipment, manifest, passengers, contracts). As Ahruman said, new developments (changes to stuff) as such are winding down. Pylon handling via script is still not available, and hopefully we'll manage to get that one in, but at the moment the priority is solving the recent trunk bugs.
We might also be updating the js engine to the latest stable mozilla one, but apart from that we shouldn't have anything major happening between now and 1.74.
Hope this answers some of the questions.