+- Southperry.net (https://www.southperry.net)
+-- Forum: Maplestory (https://www.southperry.net/forumdisplay.php?fid=15)
+--- Forum: Maplestory Discussion (https://www.southperry.net/forumdisplay.php?fid=31)
+--- Thread: Asiasoft's definition of "permanent". (/showthread.php?tid=52789)
Asiasoft's definition of "permanent". - CroM - 2012-03-23
Thorr Wrote:Sure, these are the things that I would do if I owned the game and it was a private venture. However, anyone who works in the industry will happily tell you that there is a piece of red tape that always gets in the way - Change Management. Change Management is the bane of all developers. It is supposed to exist to regulate code changes and additions across multiple versions of a product line. It is there to make sure you are putting things in the right place, etc. But, in practice, it gets in your way CONSTANTLY. With a company like Nexon who has multiple localized versions of each game product they produce, their code management software is going to be locked down pretty tightly. The smallest of changes that might take a few seconds still has to go through the entire internal change management policy. This would likely entail the following steps be followed (adapted from the Change Management policy in my own company):
1) complete documentation of the error and its cause
2) code location and proposed fix
3) creation of a new test instance for version being corrected
4) actual fix coded
5) Fix tested and submitted for approval by the product manager
6) new source distributed to the code base in use by developers of forthcoming content
7) developers determine whether the change alters their work
8) Product manager signs off on the change based on the recommendation of the other development team. If it is a minor issue with big impact, it will probably be denied.
9) Distribution team creates plan to update the product.
10) plan is approved and then scheduled
11) Product fix is put into place and given final testing before re-opening the game to the public.
It's a ton of steps. Worse, though, is that no matter how small the change is, it has to go through all of it. Such is the life of a product development programmer, which I have been for 20+ years now. The issues I mentioned are not technical marvels that cannot be overcome. They are possible excuses for Nexon not to take the time to fix the issue because of the tremendous hassle they feel it will be.
TL;DR - Nexon is likely too lazy or busy to fix the problem.
You try to teach these kids change management you are wasting your time here. I very much doubt they have the knowledge, patience or experience to understand the grey world of software design, development, testing, deployment and maintenance, as seen from the replies to your posts.
I do agree with you on your points. Its just that the more I understand the problem, the more sighs comes out with a hollow feeling that theres a lot that can be done, but yet theres only so much that they can do.
Asiasoft's definition of "permanent". - SaptaZapta - 2012-03-24
CroM Wrote:You try to teach these kids change management you are wasting your time here. I very much doubt they have the knowledge, patience or experience to understand the grey world of software design, development, testing, deployment and maintenance, as seen from the replies to your posts.
I do agree with you on your points. Its just that the more I understand the problem, the more sighs comes out with a hollow feeling that theres a lot that can be done, but yet theres only so much that they can do.
I'm not a kid. In fact, I was a programmer myself for over 20 years, until I retired. Many of those years were spent at a large, ISO 9001 certified, software house. I know how software changes work.
However, observing MapleStory, it becomes clear that Nexon does not work that way. They release bugs that would never have seen the light of day if Nexon had so much as code reviews. They have recurring bugs that prove they either don't have, or don't know how to use, version management tools.
And, as I observed in my previous post, they have shown time and again that, when properly motivated, they can implement and release fairly big changes in a very short time, even if it isn't the sort of emergency that would justify such behavior in a "proper" development environment.
Asiasoft's definition of "permanent". - x3repentance - 2012-03-24
moore4me Wrote:After Himes saying they couldnt make the chairs permanent, I love the response on page 6 by AKradian, where he says " Why can't you offer a Permanent Pink Bean Chair?
It costs too much to manufacture? You've run out of Pink Bean Leather? " That actually made me laugh out loud.
running out of pink bean leather
Asiasoft's definition of "permanent". - Pink Bean - 2012-03-24
x3repentance Wrote:running out of pink bean leather
They're made out of Mini Beans.
THEY TOOK MAH BABIES
pineapple all of you stop dragging me out of my plane of existence LOOK WHAT HAPPENS
Asiasoft's definition of "permanent". - SaptaZapta - 2012-03-29
Nexon, that master Troll, has implemented compensation for those people who received 30-day chairs instead of the perma chairs they were promised.
It's a free chair gachapon ticket.
Of course 90% or more of chair gachapon chairs also expire in 30 days, but hey, at least we get a chance at a random perma chair, right?
Asiasoft's definition of "permanent". - Kirov - 2012-03-29
I got an expiring chair that only restores MP on my Demon Slayer, cool.
Asiasoft's definition of "permanent". - ShadeCaro - 2012-03-29
Glad you met Asiasoft, at least they can accurately name predictions to the world ending while Nexon is like "HAVE A MONTH"
Asiasoft's definition of "permanent". - x3repentance - 2012-04-01
Pink Bean Wrote:They're made out of Mini Beans.
THEY TOOK MAH BABIES
pineapple all of you stop dragging me out of my plane of existence LOOK WHAT HAPPENS
Forced to the edge of extinction lol