BTS - But They Said!

[Dirty_Vo]

2ldr - Jagex promises update twice during the week but doesn't follow through.

 

Ok i made a rant about this same thing on the Rsof about a week ago before i read BTS - but they said it posted on tip.it

So the Author says "So really, the rage and upset over this is just rather stupid if you ask me." So Jagex brings back the BTS (which i love greatly) because it gives you things to look forward to.

 

First week of the month - Love story comes out.

Second week of the month - no update

Third week of the month - Dung update comes out

Fourth week of the month - Tons of players are anticipating the TT update. If i remember correctly (correct me if i'm wrong) Monday it didn't happen, Mod Emily posts that there is a delay on the update (this is before they announce that there's a week delay so I and i'm sure some others thought no worries it'll come out Tuesday, Wednesday, or Thursday at the latest.) Tuesday comes around and there's no update, a Jagex Moderator (not Mod Emily it was a guy forgot his name) say's don't worry you'll still get your update this week. Wednesday is here, I'm not at my house but i check my phone to see if the game has updated yet and hopefully id get to see some of the rewards! No how strange it hasn't happened yet, check the forums to see if people were mad then i see at the top of the page, "Game Update Delay." Can't say i wasn't expecting this but think it'll be out tomorrow, click the topic and says there's a week delay.

 

Sad and somewhat frustrated i go through the forums looking through the rants and see people sticking up for Jagex, which happens every time there's a delay there's ranters and the people that stand up for Jagex. Every time.

 

So back to the Author who wrote the Jagex times this week, the Author says "So really, the rage and upset over this is just rather stupid if you ask me."

 

So it's stupid that people rage and get upset over something like this. Jagex did not promise the update happening the week not once, but twice, and on top of the one of those promises it was the night before the week delay believe it or not.

 

Sorry for the long kinda off topic rant, even though it disappointed me I've just been dunging. But thought since the author of the tip.it times got to speak his voice to everyone that goes to tip.it and reads that, just thought I'd be the voice for the people who don't want to or are to lazy to speak against that author.

 

EDIT: i'm sure someone is going to say well you know nothing about progamming and how hard it is so you have no input. Well i don't have background with that but Jagex programmers should, and Jagex don't start working on updates the week before they release it, they spend months on updates working on them and then testing them so by them saying an update will come out, then the next day have it delayed shows how organised they are with testing their updates.

 

/rant

Hate rate appreciate lol

[Dirty_Vo]

wdf reply and HATE!!!!

[Omali]

EDIT: i'm sure someone is going to say well you know nothing about progamming and how hard it is so you have no input. Well i don't have background with that but Jagex programmers should, and Jagex don't start working on updates the week before they release it, they spend months on updates working on them and then testing them so by them saying an update will come out, then the next day have it delayed shows how organised they are with testing their updates.

 

/rant

Hate rate appreciate lol

 

I was working on my website, and I found that a few of my tags weren't working, so I dove into the code and found a rogue list tag sitting by itself, screwing up the page and completely breaking the formatting. I removed it and, upon previewing the page again, it was even worse than it was before. The editor wigged out and started duplicating several lines of code every time I would move from code-view to preview. I checked and found that the rogue list tag I deleted earlier was breaking one part of the page, but supporting an entire other section, causing the duplication (the system was trying to close the tag by copying the code, but ultimately ended up copying the same rogue tag causing the problem), because new code somehow managed to wedge itself into the old code, and separate it.

 

And that was working with Wordpress and HTML.

 

When working with any kind of programming language, new code can break existing code. No programmer in his right mind can look at a piece of code and say "I can have this fixed in _ hours," and to think so just goes to remind the rest of us that you really have no idea what you're talking about. The problem with the update rose out of an incompatibility with less-than-current generation systems that popped up at the last second. The problem was likely looked at and the engineers said "we can probably have this done by tomorrow." Tomorrow came around, and no dice. The next day, probably some things fixed, but not to satisfaction.

 

Developing software so it will work on the millions of hardware combinations is hard enough, but suddenly having a major portion of your compatibility go out the window is nothing short of the thing programmers have nightmares about in the dead of night. Talk about leaks in the brick wall, this is more akin to a hoard of Mongolians trying to knock your wall down. Bad updates get people angry, but when the game stops working people stop subscribing, and for the couple hundred whiners who are going to complain about the update being pushed back, it is far worth the money Jagex will spend fixing it, and saving those who would have quit with their game not working at all.

[blakdragon39]

Omali is quite right. That is all.

[Dirty_Vo]

EDIT: i'm sure someone is going to say well you know nothing about progamming and how hard it is so you have no input. Well i don't have background with that but Jagex programmers should, and Jagex don't start working on updates the week before they release it, they spend months on updates working on them and then testing them so by them saying an update will come out, then the next day have it delayed shows how organised they are with testing their updates.

 

/rant

Hate rate appreciate lol

 

I was working on my website, and I found that a few of my tags weren't working, so I dove into the code and found a rogue list tag sitting by itself, screwing up the page and completely breaking the formatting. I removed it and, upon previewing the page again, it was even worse than it was before. The editor wigged out and started duplicating several lines of code every time I would move from code-view to preview. I checked and found that the rogue list tag I deleted earlier was breaking one part of the page, but supporting an entire other section, causing the duplication (the system was trying to close the tag by copying the code, but ultimately ended up copying the same rogue tag causing the problem), because new code somehow managed to wedge itself into the old code, and separate it.

 

And that was working with Wordpress and HTML.

 

When working with any kind of programming language, new code can break existing code. No programmer in his right mind can look at a piece of code and say "I can have this fixed in _ hours," and to think so just goes to remind the rest of us that you really have no idea what you're talking about. The problem with the update rose out of an incompatibility with less-than-current generation systems that popped up at the last second. The problem was likely looked at and the engineers said "we can probably have this done by tomorrow." Tomorrow came around, and no dice. The next day, probably some things fixed, but not to satisfaction.

 

Developing software so it will work on the millions of hardware combinations is hard enough, but suddenly having a major portion of your compatibility go out the window is nothing short of the thing programmers have nightmares about in the dead of night. Talk about leaks in the brick wall, this is more akin to a hoard of Mongolians trying to knock your wall down. Bad updates get people angry, but when the game stops working people stop subscribing, and for the couple hundred whiners who are going to complain about the update being pushed back, it is far worth the money Jagex will spend fixing it, and saving those who would have quit with their game not working at all.

Well tell me why they didn't test this stuff weeks before release instead of saying the update will happen later in the week (they said this the night before the week delay) so that to me seems like they waited a couple days to start working whatever it is out?

[ghjkl]

They should wait until a update is 100% finished before announcing that they will release it.

[Dirty_Vo]

^ Well if they put it in BTS they should atleast be to the end testing of it

[Omali]

Well tell me why they didn't test this stuff weeks before release instead of saying the update will happen later in the week (they said this the night before the week delay) so that to me seems like they waited a couple days to start working whatever it is out?

 

Those couple of days could have been spent simply locating the source of the problem. In my website analogy, it took me a couple hours just to find the source of the issue, which was spent cross-checking HTML code. Andrew said last year that Runescape was hitting a million lines of code, and Java is much more complicated than just HTML.

 

I agree with your idea that Jagex should be finishing updates weeks ahead of time, but the thing is most developers do this. Look at Left 4 Dead 2, which was delayed several hours before release because of a hole that was found literally at the last moment.

[Sinkhan]

Well tell me why they didn't test this stuff weeks before release instead of saying the update will happen later in the week (they said this the night before the week delay) so that to me seems like they waited a couple days to start working whatever it is out?

 

You have to realize that Jagex is still a relatively small company with limited resources. With the hundreds of thousands of different hardware setups along with all the different operating system configurations, there's simply no feasible way that Jagex can perform a reasonably large test sample and then fix them. If they did that before releasing everything, you'd probably find fewer updates overall for slightly less buggy content. They still do it obviously, but there's only so much you can do.

 

Within a few days or even just hours of the release of new content, tons of players are potentially testing out that new content and thus put it under tons of different scenarios. Those few hours runs the content through the number of permutations of computers and setups that would take developers weeks if not months to fully test.

 

By releasing mostly functional updates, they can find bugs and fixes MUCH faster since we're the one's doing it.

 

There's always a fine balance to be met during the development process.

[Nomrombom]

I could barely even follow the OP :shock:

[Vulxai]

Didn't they say they had tested it, and it was only at the end of the testing phase when they found they had a problem? Correct me if I'm wrong, but I remember reading that. Which means they were sure it would work, but if you've done any programming at all, you'll know that things can go wrong even after testing it multiple times.

[Mio]

So back to the Author who wrote the Jagex times this week, the Author says "So really, the rage and upset over this is just rather stupid if you ask me."

 

So it's stupid that people rage and get upset over something like this. Jagex did not promise the update happening the week not once, but twice, and on top of the one of those promises it was the night before the week delay believe it or not.

 

waitwut? Why are you ranting at somebodies opinion? It's their opinion... Everybody has different opinions...

[Synthox]

So back to the Author who wrote the Jagex times this week, the Author says "So really, the rage and upset over this is just rather stupid if you ask me."

 

So it's stupid that people rage and get upset over something like this. Jagex did not promise the update happening the week not once, but twice, and on top of the one of those promises it was the night before the week delay believe it or not.

 

waitwut? Why are you ranting at somebodies opinion? It's their opinion... Everybody has different opinions...

Oh no...no update. Gahhh!!!! Now we will be forced to use the other million lines of code. Oh, the horror!

 

But, jagex really shouldnt say it in the bts unless it is 99-100% complete. The treasure trail update includes tons of new items and stuff. In all likelihood, one of the items was animated wrong and the end off the staff or whatever went into the player when it was used in combat. So they fixed that, saw another problem caused by the fix in the code, fixed that, and it snowballed from there. I've been building roller coasters and the like out of knex and that type of thing happens all the time. Sure, they intended for it to come out on that week, but [onion] happens. Suck it up.

 

Actually, i'm not sure if that had anything to do with the topic but im too lazy to rewrite it. Oh well.