As preparations continue to launch EiF’s unique Galactic Civil War system, the team is proud to announce one final round of testing: the week of war.
The GCW system, as written, has plenty of moving parts, and the team simply cannot test everything to the extent necessary before rolling the system out in its entirety. Of major concern are the planetary invasions, which are the heart of the system – epic battles in which factions can seize control of enemy-held planets.
These planetary invasions are built from the same core, but each planet has its own customizations. As such, they need to be individually tested to ensure everything works as expected. To facilitate this final testing, the EiF team is hosting a week of war.
Starting April 23rd and continuing through April 29th, the live server will have a planetary invasion every day. The Monday through Friday invasions will take place at 9 PM EST, which is currently the planned time for events in the final system. The Saturday and Sunday invasions will take place at 3 PM EST to allow European players to participate at a friendlier time.
(Also, a big thank you to the New Zeltros crew for willingly suspending their events for the test week!)
Participating in the GCW system this time around will net players War Fame, which will be used to purchase reward items once the entire system is live. GCW live system rewards include armor, weapon, house, and speeder schematics, as well as a few new surprises.
The rewards won’t be available yet – the awarded War Fame will be banked for future use.
The planets that require testing under the final system:
Yavin 4 and Dantooine are considered adequately tested at this point due to external and internal testing; Taanab, on the other hand, has gone through multiple iterations since the first event and needs to be retested with the new code.
This week of war testing will be a final check of the code as well as one more look at balance issues before the system goes live. (Of major concern is whether it’s too easy to defend as currently stands; the week of war should give us more data on that subject so we can make any needed tweaks before launch.)
Join us for the week of war, April 23rd – April 29th!
We will be conducting a third, and with any luck last, live server test of a GCW invasion on Sunday, April 8th at 3 PM EST. Location will be announced shortly before kick-off. Come armed and ready for both offense and defense!
Assuming a successful test, we will shortly after begin rolling out the GCW to the live server, starting with the Senate and Council election system.
Due to unexpected circumstances, we patched early this morning, and as a result a few things haven’t made it in. We’ll have a follow-up patch later this week.
*Armor can now accept armor attachments. These need to be crafted into the armor at final assembly (e.g. when a fully-crafted armor core is inserted into the final armor appearance piece).
*Armor can accept one attachment per piece.
*Armor and clothing attachments now display their stat modifier in the name of the attachment itself. This change is retroactive, but attachments listed on vendors must be pulled into inventory before they will update with the new name.
*Bioengineered pets have gotten a substantial boost. Talk to your local BE and see what she can do for you!
*High-end bounty hunting missions can now drop schematics for bounty hunter armor pieces.
*High-end bounty missions now have a smaller chance of dropping junk.
*Cloning no longer requires a load screen. (Note that this function is in testing and may be reverted if problems arise.)
*Factional cloning implemented for invasions. Defenders will be able to clone at a city’s cloners. Attackers can only clone at base camps.
*City cloners will revert to neutral status after invasions end.
*Cloning at a factional cloner always incurs wounds.
*Neutral players may clone at a factional cloner, but will incur wounds.
*Triple-incap death from a player no longer incurs decay.
*Death from a factional NPC while overt no longer incurs decay.
*Combat walkers can now only be controlled by correctly factioned players.
*Combat walkers now protect their pilots from incoming damage.
*Combat walkers can now only target enemies in front of them.
*Combat walkers no longer move or shoot without a pilot.
*Combat walkers now automatically dismount the pilot upon destruction.
*Combat walkers no longer use the rifleman speed modifier to calculate time between shots.
*Players can now use /requestLeave to set their factional status back to “On Leave” without talking to a recruiter. The time necessary to go to on leave status is dependent upon the player’s factional rank, with higher ranks taking longer to go on leave.
*Rotate left/right commands now work as before (in addition to the improved yaw/pitch/roll commands).
*Rotate left/right on the radial menu is again functional.
*Picking up an object now resets its rotation. (No more dropping items under the floor!)
*Added lootable items and schematics for previously unattainable decorative items.
(Note: lootable items are not yet in the loot tables, but will be very soon.)
*Flash speeders and flash speeder deeds are again no-trade.
*New flash speeders can be claimed with the /flashspeeder command, for the cost of 20,000 credits. (Republic credits will be fine.)
*Weapon decay has been increased. Decay for carbines and rifles has been rebalanced.
*NPC resists rebalance is approximately 50% complete. Please provide feedback on new resists to Anishor.
*Players can now use the /rattle command to speak on behalf of their pets! By targeting a pet and using /rattle followed by text, a player can make their pets speak whatever they’d like. This function is currently restricted to droids and NPC followers.
*Admin characters can now use the /rattle command to cause any creature object in the game to speak.
*Armor effectiveness slice has been adjusted to allow a slightly higher cap.
*On-planet travel no longer requires a load screen. (Note that this function is in testing and may be reverted if problems arise.)
*Newsnet terminals in starports now have additional functionality. The information on the terminals is updated realtime from the website. Check the terminals for patch notes, GCW headlines, and information on upcoming events!
As promised, our Friday Feature today is about an element of the upcoming GCW system: planetary invasions.
Standard disclaimer: all information below is subject to change during the development and adjustment process. While we believe this will remain accurate, unforeseen circumstances are always a possibility.
In a previous Friday Feature, Political Power, we discussed how players could be elected to their chosen faction’s ruling body, which manages the war effort by selecting enemy planets for invasion, engaging in a sort of dejarik game against the opposing faction’s ruling body.
Today’s feature is about the boots on the ground – how planetary invasions work!
Stage 1: Forces MarshalIt may be a bit of a misnomer to call this a “stage”. As an invasion kicks off, initial defense forces rally around the defending starports. Defenses generally consist of mid-sized squads of troopers, as well as multiple defense turrets. Large-city starports deploy autoturrets both in normal defensive positions and inside the landing ring to prevent attacking troops from bypassing the defenses by using civilian transport.
Attacking forces spawn at a nearby beachhead camp and prepare to march on the target starport. These forces usually have large squads of troops and, depending on the size and value of the target, combat walkers ranging from small AT-RTs all the way up to massive AT-ATs. The walkers are reserved strictly for players; unlike the troops, they will not act without a living commander.
During the “forces marshal” step, PvP zones will be established. Any player entering the invasion zone will be vulnerable to attack from other players.
Finally (though it may not be available for the NYE live server event), players will be able to use factional trooper coordinators to travel directly to a starport (if a member of the defending faction) or to a beachhead camp (if a member of the invading forces) of the world being attacked.
Phase 2: Forces Engage
Offensive forces marching on the target will inevitably clash with the static defenders. NPC armies will engage, and without player involvement the defenders will have a small advantage given their autoturrets. Attacking forces, however, can use their assault walkers to crack through the defenses and make their way into the target starport.
Both offensive and defensive forces will regularly respawn and maintain a running battle throughout the invasion time. However, defensive autoturrets and invading walkers will not respawn, and once knocked out of the fight are out for the duration of the invasion.
Phase 3: Hostile Takeover
Attacking players need to force their way into the starport and take control! To seize control requires five players – a bounty hunter, a smuggler, a doctor, a commando, and a squad leader.
The bounty hunter will initiate the takeover by jamming the uplink terminal. (This requires the Investigation II box and grants a healthy chunk of investigation XP!) The minigame for an uplink jam is a simple higher/lower guessing game.
The smuggler then slices into the security terminal. (This requires the Slicing I: Terminals box.) This process follows the standard slicing minigame; it is highly recommend the smuggler be prepared with a molecular clamp so he does not screw up the slicing process!
The doctor then uses the override terminal and provides a DNA sequence. It uses a gene letter matching minigame with A-T and C-G DNA sequencing.
The commando switches alignment on the power regulator next. The minigame requires the player to switch all the switches to either “on” or “off”, with the catch that flipping one switch will affect other switches as well.
Finally, the squad leader uses the HQ terminal to seize control of the starport!
A successful invasion requires the attacking faction to seize all the target planet’s starports inside the time limit.
All the starports must be seized.
The invasion system is programmed so that we can adjust the time limit on a per-planet basis (as well as adjust attacking and defending forces). For initial purposes of the GCW, all planets will have a 60 minute time limit to successfully complete an invasion.
When the GCW is fully released, we will be monitoring the GCW closely and adjusting as necessary to ensure both factions have a chance at seizing planets. We have no illusions that it will be perfect right out of the box; monitoring and adjusting is an important and necessary step.
The dev team is proud of the invasion system, though we ask that players understand the limitations of the SWGEmu code. Elements we are using to pull this off are as-of-yet unfinished, particularly in regards to the NPCs, and some wonky behavior results. We’re waiting in part for the SWGEmu team to finish their AI revamp to smooth out some rough edges.
Good luck, have fun, and may the Force be with you!