A staggeringly large amount (if not an overwhelming majority) of people who still currently play have one or multiple rank 50's. This is common knowledge.
A staggeringly large amount (if not an overwhelming majority) of people who still currently play have one or multiple rank 50's. This is common knowledge.
Not to sound wierd.... But i think you guys are mixing up what a que system did. From my experience on que systems. Is that if you have a full party, you can enter no problem. But if you are not in a full group. You would que up, till there is enough people. Then be placed in a spot. Most instance raids on WoW have multiple layes to alot a ton of groups through. I've never seen an instanced raid que. Only for something like battle grounds on WoW.
Oh and the dynamis hour lass got lowed to 500K. it may even be lower then that by now. I didn't like how SE did dynamis. People got really snobby about it.
Thank you, hope it is more than 20 parties at a time. (at very least). I don't think you will have trouble to make just 20 instances, since other game I played could make 100+ instances at the same time. It is all up to how you would like people to wait (waste) time outside.
Yes. The problem is definitely SE's "wording." You're totally right to blame them. If you -- with your superior writing skills -- had done the post, you'd have made it clear they were talking about instanced content. Which they didn't do, right? I mean, just look at what they said: Wait, isn't that exactly what you quoted? And doesn't it use the word "instance" right there in the sentence?
Hmm. Maybe SE's not to blame for your posts, after all. Awesome. I love how you deny, deny, deny that they're using instances, and then say that you expected that they'd use instances. Yeah. You knew it all along.
And if you think instance dungeons are "quirky technology," then I'm still not convinced you know what "instance" means. For example, it doesn't mean that they "create[d] several of the same zone with multiple rout[e]s." It means that they created one zone, and they run it on multiple instances.
k first off i was being sarcastic because i felt stupid for not getting what they said in the first place. sarcasm can be hard to get online so im not mad that it wasnt caught on.
second, let me show you this-
"since they use their own quirky *technology and do things differently than i *would it really wasnt surprising to me that *theyd just create several of the same zone with multiple routs and just call it an instance"
* the quirky technology im talking about is their hardware and software which have been noted by several people to not be optimized for creating an MMO, if those people were wrong and everything their side is great then... woops? either way i know im right in this aspect so ague it all you want.
edit, oh wait what i mean here is, i know im right because things would have been alot easier if they just went with at least the cry engine... or something with instructions.
* there are many things lots of us would have done differently than they
* what i said was (which i MEANT prior to this thread), i was expecting them to create a set number of the same zone awaiting occupancy- which are not instances. this and my poor understanding of their wording led me to think there were going to be multiple parties in one "instance". i use quotes here because i was expecting them to label these ever existing zones falsely as instances.
at what point did i deny they are using instances and then say i expected them to all along?
the last part of my sentence was referring to me expecting them to falsely call what they are creating instances. that was my expectation prior to me realizing they actually are using legitimate instances---- so one of my original questions still stands, how many at once?
wow, you non the less misunderstood what i said just as i them.
I doubt the technical limit on instances will be a single digit number. WoW is able to handle many instances of the same instance (lol). Heck, they even have a cross-world dungeon system (which, while I don't like the idea, is impressive for how difficult it must have been to implement).
Don't underestimate SE.Quote:
I doubt the technical limit on instances will be a single digit number. WoW is able to handle many instances of the same instance (lol). Heck, they even have a cross-world dungeon system (which, while I don't like the idea, is impressive for how difficult it must have been to implement).
They managed to have an auction-house replacement that constantly crashed
and currently reached its limits in U'dah although servers are almost empty.
ZOMG WOW can do like 20-30 instances at the same time why can't SE do it!
a.) we don't know the limit yet so why complain and speculate when we have no info yet
b.) the total poly count in 1 of these instances looks very VERY high, with multiple paths and several level's to clear your talking one massive instance, I bet we get 10 groups at a time and I doubt much wait times when it does go live.
Does anyone have more experience with WOW who could also compare poly's within an instance? I think from my rough knowledge of programming (yes I program for a living-SQL client server socket stuff) I'd say the conversion might be on the order of 1 to 10. Where 1 instance of these new dungeons is about 10 in a typical WOW instance.
edit: Nevermind, not worth it going into a discussion of poly count and server load, besides that is going off topic.
I just hope we could get a clear answer stating # of groups per instance, and amont of concurrent instances.
I want to clarify a few things; While I can't disclose the number of instances that are created at the same time, I can assure you it is not a system where only one instance is available at a time. So if a group is already tackling the The Dzemael Darkhold raid, other groups can still enter their own instanced version of it. There won't be multiple parties inside of an instance, either. Your parties' raid is exclusive to your group only. We look forward to your comments and discussion once you all have had a chance to try the raids out when patch 1.18 hits. :)