Forums | Chat | News | Contact Us | Register | PSU Social |
PSU: Because Everquest sucks
Forums | Chat | News | Contact Us | Register | PSU Social |
Home | Forum | Chat | Wiki | Social | AGN | PS2 Stats |
|
|
Thread Tools | Search this Thread | Display Modes |
|
2012-06-05, 07:27 PM | [Ignore Me] #2 | |||
First Sergeant
|
Now that we got that out of the way , the MAX that we saw were of people brand new to the game. Plus there was not that much unit cohesion, so an isolated MAX unit against multiple agile infantry, especially outdoors, would lose. I wouldn't worry too much. |
|||
|
2012-06-05, 07:33 PM | [Ignore Me] #6 | ||
Lieutenant Colonel
|
Because I don't care to actually type very much lately, heres an excerpt from wikipedia:
Pre-alpha Pre-alpha refers to all activities performed during the software project prior to testing. These activities can include requirements analysis, software design, software development, and unit testing. In typical open source development, there are several types of pre-alpha versions. Milestone versions include specific sets of functions and are released as soon as the functionality is complete. Alpha The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white box techniques. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release. Alpha software can be unstable and could cause crashes or data loss. The exception to this is when the alpha is available publicly (such as a pre-order bonus), in which developers normally push for stability so that their testers can test properly. External availability of alpha software is uncommon in proprietary software. However, open source software, in particular, often have publicly available alpha versions, often distributed as the raw source code of the software. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be a feature complete. Beta Beta (named after the second letter of the Greek alphabet) is the software development phase following alpha. It generally begins when the software is feature complete. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release and this is typically the first time that the software is available outside of the organization that developed it. The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software, willing to test the software without charge, often receiving the final software free of charge or for a reduced price. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a preview, prototype, technical preview (TP), or early access. Some software is kept in perpetual beta—where new features and functionality are continually added to the software without establishing a firm "final" release. Open and closed beta Developers release either a closed beta or an open beta; closed beta versions are released to a restricted group of individuals for a user test by invitation, while open beta testers are from a larger group, or anyone interested. The testers report any bugs that they find, and sometimes suggest additional features they think should be available in the final version. Examples of a major public beta test are: In September 2000 a boxed version of Apple's Mac OS X Public Beta operating system was released. Microsoft's release of community technology previews (CTPs) for "Longhorn" in January 2005. Open betas serve the dual purpose of demonstrating a product to potential consumers, and testing among an extremely wide user base likely to bring to light obscure errors that a much smaller testing team might not find. Release candidate A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bug. A release is called code complete when the development team agrees that no entirely new source code will be added to this release. There could still be source code changes to fix defects, changes to documentation and data files, and peripheral code for test cases or utilities. Tl;dr: Beta is beta. They can balance later.
__________________
Retired NC CR5, Cerberus Company. Not currently playing PS2. Anyone with a similar name is not me. My only characters are listed in my stats profile here on PSU. |
||
|
2012-06-05, 08:16 PM | [Ignore Me] #7 | ||
Corporal
|
From I saw in the video, MAX suits got eaten alive by ES main battle tanks and Lightning tanks, so I'm not too worried about them. Yes, they are a force to be reckoned with indoors (woe to the COD kiddies when they try to run and gun quick scope against a MAX for the first time ), but come on, all of us here know a MAX can be solved with a few boomers, an AV weapon, or just running away behind cover really fast.
What I'd be worried about is a group of MAXes backed up by good engineers and medics with their pew pew heal/repairs going crashing into a base. That's going to be some glorious ass whooping right there if you are not prepared for it. The funny thing about "OMG rush!" tactics in Planetside though is you can prepare for them, or get buried by them, as this is a massive strategy game at heart as well as an FPS. |
||
|
2012-06-05, 08:23 PM | [Ignore Me] #9 | ||
Lieutenant Colonel
|
ohrly? you mean to say everything is final?
__________________
Retired NC CR5, Cerberus Company. Not currently playing PS2. Anyone with a similar name is not me. My only characters are listed in my stats profile here on PSU. |
||
|
2012-06-05, 08:36 PM | [Ignore Me] #13 | ||
Sergeant
|
I liked how they weren't completely impervious to small arms fire.
With solid medic/engineer support, though, yeah - they're going to be an absolute terror.
__________________
All the world that's owned by idle drones is ours and ours alone. We have laid the wide foundations; built it skyward stone by stone. It is ours, not to slave in, but to master and to own. While the union makes us strong. |
||
|
2012-06-05, 08:41 PM | [Ignore Me] #15 | ||
Captain
|
It took, what, 3 Deci shots to kill one back in the day? Now they can actually be hurt by small arms, but with that hit point pool they should retain their defensive and siege breaking capabilities.
The VS MAX is definitely the most agile... in its sprint/run mode it seems to be able to keep up with Agile-armored grunts. |
||
|
|
Bookmarks |
|
|