Runes of Magic US / AU

Idk.

I like new zones. I like questing to slowly explore the zone. Waiting one week was fine, but that's about it.

Not a word was spoken as to why it hasn't been enabled. Is it because RW has yet to put in values? An exploit has been found? It is completely unplayable currently (buggy, etc)?

Do not see why they can't say something like that. Make it vague, but make it said. Would be nice.

Quoted from "SaitoHajime"

Basically, a bit of everything you listed in your question post, but I just can't be specific simply for the fact that the details are internal information.

What's so secretive about how an unreleased instance is broken?

never does a company want to admit what is wrong with a part of their programming. More importantly ... it doesn't matter for us gamers. We don't need to know. All we NEED to know is 1) that it isn't ready and 2) a possible time it might be ready (if possible).

I have never understood why people think that a company needs to disclose internal issues/problems/delays. No video game company gives the in depth reasons as to why they are delay something. Never do they say "ohh we found xyz exploit" and the reason is that they don't want people to then try to repeat said exploit later. By keeping it secret... less people will try to exploit it... whether it is fixed or not. New tech companies don't tell people why they delay launches or patches in depth. TV companies don't release information about upcoming promotions or reasons why a promotion was removed...


It is not common practice (if it has ever been a practice), that the customers are given full or mostly full disclosure of internal workings/errors. Companies just don't do it... so why expect it here?

It is not open, the reason why is.. it isn't ready. When will it be open? When it is as good as they can provide.


Really that is all they owe us as a company. I know in the technology age, people think that they are more entitled to the information... You aren't.

Quoted from "Dkjester"

never does a company want to admit what is wrong with a part of their programming. More importantly ... it doesn't matter for us gamers. We don't need to know. All we NEED to know is 1) that it isn't ready and 2) a possible time it might be ready (if possible).

I have never understood why people think that a company needs to disclose internal issues/problems/delays. No video game company gives the in depth reasons as to why they are delay something. Never do they say "ohh we found xyz exploit" and the reason is that they don't want people to then try to repeat said exploit later. By keeping it secret... less people will try to exploit it... whether it is fixed or not. New tech companies don't tell people why they delay launches or patches in depth. TV companies don't release information about upcoming promotions or reasons why a promotion was removed...


It is not common practice (if it has ever been a practice), that the customers are given full or mostly full disclosure of internal workings/errors. Companies just don't do it... so why expect it here?

It is not open, the reason why is.. it isn't ready. When will it be open? When it is as good as they can provide.


Really that is all they owe us as a company. I know in the technology age, people think that they are more entitled to the information... You aren't.

Couldn't have said it better myself.

Short answer: It's not ready.
Long Answer: It's not ready and we do not have any news on when it will be. Sorry, but that's the fact. Even if we did know, we couldn't tell you. It is being worked on.

I dont know if i fully agree with that concept :-\ You're free to run your company however your choose, but many video game companies, and many software engineering companies, do release information about bugs after they've been fixed so that if they crop up again people can see the bad behavior and report it. Openness and transparency helps to improve security, which is why every major encryption algorithm and most critical security protocols are totally open to the public for review. Thats why RFC's (request for comments) are a thing. Here, look at https https://tools.ietf.org/html/rfc2818 and pleanty more https://tools.ietf.org/html/. clearly im not saying to release your full protocol and source, this is a private company of a less critical nature than say how internet traffic is encrypted and transferred. we dont need that level of detail because, frankly, your product does not matter nearly as much. But to say that transparency is a bad thing is a horrible misunderstanding of the software development processes.

Clearly if you havent fixed the issue yet, dont disclose it because that would be dumb. But after it is "fixed" it SHOULD be disclosed to some degree.

I don't think it should be disclosed per say..


Because some exploits have come back after patches (I am not sure why they come back... but like for instance.. Targonhaul, was fixed, then was exploitable again, then fixed again. Telling people about the exploit and with the programming history of RW..... means you are telling people what to check to see if it ever "unfixes". That is why I 100% agree with them not disclosing it.. no matter.

while the details might not be good to release, a simple, official, "the instance is bugged" or something would be nice to hear. not silence.

Quoted from "Dkjester"

I don't think it should be disclosed per say..


Because some exploits have come back after patches (I am not sure why they come back... but like for instance.. Targonhaul, was fixed, then was exploitable again, then fixed again. Telling people about the exploit and with the programming history of RW..... means you are telling people what to check to see if it ever "unfixes". That is why I 100% agree with them not disclosing it.. no matter.

Thats exactly the reason it SHOULD be disclosed. People will memorize every bug thats ever been found and test it from time to time. Then you just have one or two people who know the bugs looking for them instead of everyone looking out and reporting them.

Quoted from "Darwec"

Quoted from "Dkjester"

I don't think it should be disclosed per say..


Because some exploits have come back after patches (I am not sure why they come back... but like for instance.. Targonhaul, was fixed, then was exploitable again, then fixed again. Telling people about the exploit and with the programming history of RW..... means you are telling people what to check to see if it ever "unfixes". That is why I 100% agree with them not disclosing it.. no matter.

Thats exactly the reason it SHOULD be disclosed. People will memorize every bug thats ever been found and test it from time to time. Then you just have one or two people who know the bugs looking for them instead of everyone looking out and reporting them.

Problem is that the people testing it aren't reporting it. Certain guild had a member using said exploit again in secret to profit. Thankfully someone found them and reported them and they are on vacation. However, that person profited for a month at least till they had the proof to ban him. I would be with you if players reported the bugs, not exploited them for gain..... which is what they do. They keep it quiet and profit, which is why as a gamer community we can't be trusted with that information......

Sad fact, but true.

I don't see how the bugs with new content have to do with bugs with old content. Say if the first boss in Pillars of Morfan is broken... how would them telling us that also tell us that some bug in some old content has also re-appeared? And right now we assume Pillar of Morfan is broken already anyway.

Well sometimes they make a patch and it reverts old issues that were fixed and are not anymore. Let's just go on a limb here and stay with me:

You got the person patching the new content, getting late, has a deadline from his boss and pressure. Start doing the programming for the patch, oops, messes up and deletes a bunch of it by mistake, he still has the unpatch one standing on another screen, CTRL-C then CTRL-V, phew!!!, boss comes in, screams at him/her, when is this gonna be ready damn it?? blablabla!!!! yes boss yes boss i'll get it done boss. Then goes back to finish his work, scared as crap to lose his/her job. Altough copying and pasting worked, forgot that that version had bugs from the previous patch and re-activated them with the copy and paste.

So scared of losing his job and stress, gives the new patch to be installed on the server and make sure not to make his/her boss scream again. All is good until someone realizes that their is something wrong, people camping known exploits and getting benefit from it and messing the servers economy even more. Then the boss goes to see the employee and say : YOU FIRED!!!.

Ya mistakes happens when people are put under stress and screamed at.


So if it is not out yet, it must be a good reason, do you think that GM's aren't tired of everybody whining about this new instance? All the big babies that say nothing is worth running for them etc, try to run lower people and help them out discover the game and have fun, show them the ropes. Ya noobs and scrubs aren't worth the time of day to you, but people should just remember who they sell diamonds too, remember those that are helpful and willing to do stuff with you. We have good people on Reni, good endgamers willing to help us out. Others not so much and looking at their own belly button all day and thinking Gameforge owns them anything, they don't.

Give them a break and they will get it done when it is ready

You assume Runewaker has dedicated employees working on Rom, which I highly doubt. I would bet they have a team of employees that work on multiple games. And if that boss is screaming it is about a newer more important game. There is no way ROM is a big money maker for Runewaker as most of their other games are much more populated and newer. It is an afterthought and from the way the refuse to fix many things shows me that.

Whenever we (my company) asks for software changes/upgrades. The company that runs the system sends us a bid, showing how many hours (= cost) it would be to fix/change a issue. I would not be surprised if this was the model for Gameforge.

Quoted from "Mrpushpop"

You assume Runewaker has dedicated employees working on Rom, which I highly doubt. I would bet they have a team of employees that work on multiple games. And if that boss is screaming it is about a newer more important game. There is no way ROM is a big money maker for Runewaker as most of their other games are much more populated and newer. It is an afterthought and from the way the refuse to fix many things shows me that.

Whenever we (my company) asks for software changes/upgrades. The company that runs the system sends us a bid, showing how many hours (= cost) it would be to fix/change a issue. I would not be surprised if this was the model for Gameforge.

#scrumlife?
Yeah thats how we do it too.

Anyways, the gms did give us an answer, and the answer we wanted. Flipping everything is broken from bugs to unimplemented features to exploits. So. yeah. GG.

Any company that doesn't have core of dedicated employees working on a particular system they are maintaining will quickly find that savings from that will be far far less than expenses when system needs work. It is not realistic to assume that there is no ROM team at RW.

next patch says Pillars of Morfan will be open.. woohooo.


Also crafting festival... here is to the hope we can go above 75 lol.

DK i am already level 89+ on all crafts and gathering at 100 on most my toons loll, i should be good for a while hahahaha ;-) Hope we get new special recipes!!! tha tthey won'T put in IS 3 months later ;-(

GO CRAFTING FESTIVAL GO!!!! BEST FESTIVAL EVER!!!!!!!!

pillers gonna be open.

only took like a month.

i guess late better than never :/

well I mean I think it is good though.

I mean new level cap, I went around quested, got most of our chars up to level max with dailies, got our mains to 87/87, stocked up some stats..... now when I am winding down a little, there is a new easy instance that I can hopefully farm int/ma attk stats out of lol.

I think it was a good timing.

Yeah Zid, I have been too lazy for my crafting, but if they put in one more recipe, 85 should be achievable, Most of mine are 80. Just would be nice to not have to farm runes lol.

yyyaaaaaaaaaassssssssss finally a reason to start playing this game again. hopefully it wont be another GoH where it's one and done.