Particularly problematic were the UI programming tasks for each game system. In contrast, programming and scripting resources were overburdened. At the time we made these decisions, we were ahead of schedule on world development and on schedule with art assets. Systems were cut or postponed based largely on the programming and scripting time required. In general, we only wanted to push out systems that can still be integrated post-launch. We wanted to postpone rather than cut a system. It also does nothing to prevent the team from being spread too thin. In most cases, just implementing a system’s core functionality is 80% of the work, so trimming is only valuable to a point. Although we continued to trim assets and small features from the game, this “nickel and dime” approach wasn't actually increasing our efficiency. We’d wanted to cut or postpone entire systems. When evaluating the systems and features, we used the following criteria to determine if a cut or postponement made sense (and we went through basically *every* system and feature): Dark Jedi (okay, this is really a "feature", but still…)Īt that time, we also began work on our Live Team schedule, which provides a plan for implementing the postponed systems within the first seven or eight months after launch. The most important of these systems were: Rather than attempt to do everything at once and have it all turn out mediocre, we wanted to focus on fewer features and do them all really well (Rather than 20 species, we only have 8, but each species is incredibly customizable - far more so than you'd get if we had pushed for 20).Īs we moved forward and continually revised our schedule, it became apparent that the postponement of several significant systems would allow us to release the game sometime in mid-April. In general, our philosophy has always been that we wanted a polished, stable product at launch. Here, I want to try to explain why these decisions were made. But, we have decided to postpone a few features until after launch. While we have changed some aspects of the design and trimmed here or there, in general we were reluctant to permanently kill a design feature, especially if it had already been discussed here on the boards.
However, as BoShek noted in a previous post, Star Wars Galaxies is a living, growing game. As with any game development process, we go through constant revisions on the design in order to both tighten the game by focusing on what turns out to be the most fun, and put together a quality game that actually sees the light of day. Read on for the entire list!!!!Īs many of you who have been part of our community since the outset probably realize by now, our feature set list is missing a few things. Some of these include Dark Jedi, player cities, and player owned vehicles. The SIZE_IN_MB is the size of the partition you want to create, in MB.Haden Blackman, Producer, has posted at the SWG website that a few of the promised features will not be available at the release.
create partition logical size=SIZE_IN_MB – use this command to create a new logical partition.The SIZE_IN_MB is the size of the partition you want to create, in MB. create partition extended size=SIZE_IN_MB – use this command to create a new extended partition.create partition primary size=SIZE_IN_MB – use this command to create a new primary partition.assign – use assign to assign a letter or a mount point to the current active partition.active – use the active command to set the focus on the current partition to be active.list volume – use list volume to get information about each volume available on the computer.list partition – use this command to get information about each partition available on a specific disk.list disk – use list disk to get summary information about the available disks on your computer.detail volume will deliver information about the current volume.detail partition will deliver information about the current partition.detail disk will deliver information about the current disk.select volume – use this command to set the focus on a specific volume.select partition – use the select partition command to set the focus on a specific partition.
0 kommentar(er)
