Jump to content

Maintenance... still?


Dankaru

Recommended Posts

Star Wars™: The Old Republic™ – 1.1.4 Patch Notes

Because development is ongoing during testing, it should be noted that all changes and updates listed in the patch notes should be considered incomplete and are subject to change or removal before release to the live servers. The Public Test Server patch notes will be provided in English. The final release notes will be provided in English, French, and German when the content is moved to live servers.

 

General

 

The key formerly bound to /bug can now be mapped to any action and no longer opens the /bug window. The command is no longer able to be bound to a quickslot, but player can still type /bug in chat to open a new bug report.

Classes and Combat

 

General

 

Using abilities with indirect targeting (such as area of effect abilities) will no longer cause players to be flagged for PvP if a PvP-flagged player from the opposing faction is within the ability’s range, and the ability will have no effect on the PvP-flagged player.

Imperial Agent

 

Operative

 

Medical Therapy: Kolto Probe and Recuperative nanotech will now properly benefit from this skill.

Bounty Hunter

 

Powertech

 

Carbonize: PvP armor for Combat Tech will no longer prevent this skill from stunning enemies.

 

Flashpoints and Operations

 

Operations

 

Eternity Vault

 

Casting Mind Trap will no longer cause Soa to lose threat against his primary target.

Karagga’s Palace

 

G4-B3 Heavy Fabricator now has fewer hit points in Normal Mode.

 

Items

 

Vendors

 

“Show Usable” now properly filters to only show equipable items.

 

Missions and NPCs

 

Missions

 

Republic

 

Unlikely Allies: Resetting no longer requires players to abandon and re-acquire the mission in order to complete it.

 

PvP

 

Warzones

 

General

 

Fixed a queue interface exploit that allowed players to bring additional players into a warzone. While imbalances can still happen under specific circumstances, the issue can no longer be intentionally triggered by players in this way. *UPDATED*

Alderaan Civil War

 

The Eastern Turret no longer fires twice under some circumstances when it is captured by the Imperials.

 

UI

 

General

 

Added a /version command.

Added several new preferences for cooldown appearance:

Show Ready Flash: Toggles a bright flash when an ability finishes cooldown.

Show Global Cooldown Ready Flash: Toggles a bright flash when an ability finishes global cooldown.

Cooldown Style: Changes the art style for the cooldown graphic.

Global Cooldown Style: Changes the art style for the global cooldown graphic.

Show Cooldown Timer: Toggles cooldown time text on top of the ability icon in the quickbar.

Bug Fixes

 

Sorting will now function properly in the Guild Window.

Items placed in a quickbar are no longer removed when training abilities.

Using Shift + Right Click to split a stack of usable items will no longer cause the item to be used.

 

Miscellaneous Bug Fixes

 

Players will no longer experience occasional disconnection when purchasing Crafting Materials from the GTN.

Link to comment
Share on other sites

why do ppl get so burthurrt about this... dude get over it. it said 9am central.. so it will be done soon...

 

if needs these updates to fix things.. alot of things... i look forward to these because everytime it means the game is getting better... its evolving ... get with it

and stop waisting ur time on the forums about somthing u cant change.

Link to comment
Share on other sites

I still don't understand how people can not get a simple small patch done in 7 hours. If you think its going to take 8 then tell people 10 and when its done early people are HAPPY. Being told 7 hours and taking 9 is just bad business.

 

This.

 

It's IT rule #1. Under commit and over perform. If you think something will take X hours tack on at least 25% more time just in case something unexpected happens.

 

That aside I know how it feels when the **** hits the fan. Keep in mind the guys actually applying the patches and running the maintenance aren't necessarily the guys that are responsible for the code itself. In fact more than likely they had to make some angry calls to get the programmers out of bed when something didn't apply correctly.

 

That said a robust server infrastructure should allow for rollbacks (i.e. Database journaling) if anything goes catastrophically wrong. Which leaves the likely scenario that they just don't have a good handle on estimating how long these changes will take to roll out.

Link to comment
Share on other sites

×
×
  • Create New...