Update Notes: Thursday, August 6, 2015

Written by Feldon on . Posted in EQ2, Game Updates & Maintenance, PvP/BG/Proving Grounds, TLE/Prestige Servers, Tradeskill

From the EQ2 Forums:

GENERAL

  • Fixed a display issue where starting equipment was not showing correctly during character create.
  • Fixed an issue where some nameplates would show incorrect names.

Time-Locked Servers

  • Fixed an issue where the house item edit mode wheel was not responding.

Time-Locked PvP

  • PvP kills will now reduce faction with city guards.
  • Guards in city zones will now assist citizens in PvP if that citizen is attacked while in proximity of the guard.

POPULATION / ZONE PROGRESSION
PvP General

  • Guards in City Zones will now come to players’ aid in PvP combat more often. If a guard, in a city zone, AKA carnage flag zone, witnesses any hostile act against a player of his or her city faction they will assist that player.
  • NOTE: Guards in non-city zones such as Antonica and Commonlands are not affected. Only in city zones like Halas and Darklight Woods.

TRADESKILLS

  • Fixed a bug where all of your tradeskill abilities would be greyed out when you start tradeskilling.

Trackback from your site.

Comments (4)

  • Pipsissiwa

    |

    Glad they’re finally fixing that tradeskill buttons being greyed out bug. Its a crazy trivial cosmetic thing but I find it really annoying for some reason. /shrug

    Reply

  • madrat

    |

    Happy dance, tradeskill abilities have been fixed. 🙂

    Reply

  • Korvan

    |

    While they may have tightened a few bolts, they definitely loosened some screws with this update. A lot of people are talking about taking large, sporadic hits to their framerates (which creates this “hitching” effect, even in areas that aren’t particularly crowded). I had a guildmate who’s FPS was dropping into the single digits inside Nek Castle last night.

    Then there are those random crashes to the desktop, with or without errors indicating that DirectX being out of memory. Usually it happens after a long-ish session (a few hours), and apparently the client is still leaking memory like it’s 2005.

    Reply

  • Tom tucker

    |

    I second that the client has a memory leak.maybe due to the forced file that got introduced with the client.

    Reply

Leave a comment

You must be logged in to post a comment.


Powered by Warp Theme Framework