[Notice] [Complete] Unscheduled Log-In Server Maintenance - July 14, 2016

[Notify]

http://maplestory.nexon.net/news//15020/

We will be performing an unscheduled login server maintenance on Thursday, July 17, 2016 at 10:30 PM Pacific (1:30 AM Eastern).*The maintenance will last approximately 1 hour. During this time, players will not be able to log into the game. Players already in the game will not be affected.*

Thanks for your patience!

Time:

Thursday, July 17, 2016
Pacific: 10:30 PM – 11:30 PM**
Eastern: 1:30 AM – 2:30 AM

What will be unavailable:

• MapleStory login server

Changes and Updates:*

• The Blaster Damage Skin and Summer Damage Skin Coupons will no longer cause the game client to crash and will now be tradeable. If you already have either of these coupons prior to the login server maintenance, please log out and log back in after the maintenance before using the coupons.*
• The Damage Skin Random Box is now back on sale for both Reboot and Non-Reboot worlds.

[SaptaZapta]

Interesting.

I always thought that Untradeability was part of the item definition, not in the instance data.

[Notify]

*

[Complete]*The log-in server maintenance has been completed as of 11:05 PM Pacific Daylight Time.*


*

We will be performing an unscheduled log-in server maintenance on Thursday, July 14, 2016 at 10:30 PM Pacific (1:30 AM Eastern).*The maintenance will last approximately 1 hour. During this time, players will not be able to log into the game. Players already in the game will not be affected.*

Thanks for your patience!

Time:

Thursday, July 14, 2016
Pacific: 10:30 PM – 11:30 PM**
Eastern: 1:30 AM – 2:30 AM

What will be unavailable:

• MapleStory login server

Changes and Updates:*

• The Blaster Damage Skin and Summer Damage Skin Coupons will no longer cause the game client to crash and will now be tradeable. If you already have either of these coupons prior to the log-in server maintenance, please restart the game client before using the coupons.*
• The Damage Skin Random Box is now back on sale for both Reboot and Non-Reboot worlds.

[maplefreak26]

Interesting.

I always thought that Untradeability was part of the item definition, not in the instance data.

They added a client hotfix functionality in the past couple of patches (I think it was right before or around Reboot). Only JMS, CMS, TMS, and GMS have this capability IIRC.
That Data.wz in your MapleStory folder has all the hotfixes that Nexon has applied to the game files.

[SaptaZapta]

They added a client hotfix functionality in the past couple of patches (I think it was right before or around Reboot). Only JMS, CMS, TMS, and GMS have this capability IIRC.
That Data.wz in your MapleStory folder has all the hotfixes that Nexon has applied to the game files.

I see.
That explains why they didn't need a client mini-patch.
But it doesn't explain what they needed to fix in the login server.
Unless the login server is responsible for pushing out the hotfixes to the clients, and they forgot to update it in yesterday's maintenance?

[maplefreak26]

Unless the login server is responsible for pushing out the hotfixes to the clients, and they forgot to update it in yesterday's maintenance?

Yeah. The Data.wz information is sent to the client right before you see the Opening.avi video. And I'm guessing maybe they couldn't verify/test the hotfix update (or forgot they even had this functionality) in time before the servers came up for the previous unscheduled server maintenance.

The client got the hotfix capability in the client around v14x and they never really used it until they added the Data.wz file half a year ago. I even remember a private server using this functionality before GMS ever got around to using it.

[SaptaZapta]

The previous maintenance was scheduled, and was extended 3 times before they gave up and removed the damage skin boxes from the Cash Shop and updated the Cash Shop Specials notice before the servers came up. They did have time to test and knew the client was crashing whenever it encounters the changed items, they just didn't have a clue about how it was supposed to be updated.
I guess they only have one person who knows anything about the hotfix functionality. Possibly someone in another team (CMS or JMS). So they had to wait until now for a consult.
Such professionalism.