This is my issue with his posts. It seems odd to me that someone would join an old community just to champion a single thread/game. It screams shill. Like he typed TESO in google, saw rerolled and registered here just to champion the game. Not that I really care if someone does that, but when it comes to listening to someone with a very suspicious posting history, or a long time member who is active all over they place... the new guy loses.
The Elder Scrolls Online
- Thread starter Anomander Rake
- Start date
-
Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!
Go here and give us your nominations!Who's been the biggest Asshat in the last year? Give us your worst ones!
Yea I've had that's pointed out to me several times. Too bad the old FOH forums aren't around anymore so someone could confirm how long I've been lurking. Like I said a long time ago in this thread, I applied for posting rights but was never granted them. When I joined the FOH board guild in Tera, I had to send Oloh a PM to get an invite.
If a discussion thread ever pops up here to discuss Ngruk, I could relate some personal conversations we had back when we playing WoW together.
I guess so, based on what they've passed on. It'd be far better if they dynamically appeared or they had specific large raid like public quests in areas that fit the setting, instead of pushing so many single player quests. Maybe that changes.
Rift really did a poor job of, well, Rifts. It was like Warhammer's PQs but without the depth, rewards, or incentive.
Vitality
ＨＵＳＴＬＥ
- 5,808
- 30
These last few pages have just gotten hard to read.
The general stance is that weekend beta environments with a high load generally increase the variance in combat fluidity and impact delay.
Whether you're a shill, a reverse-shill, or a neutral I'm sure you can all agree on the above statement. Furthermore I'm sure you can all agree that this is an issue that has caused games in the past to become disasters.
No game "Should" sacrifice fluidity for gated animations. It's the same discussion the COD boys are having over the knife animations delaying their game to the point where they particularly avoid knifing.
But in our case, we'll just particularly avoid the game if it gets that bad.
"Mileage may vary" is just as good of an opinion as "Can't be sure til next weekend"
Both points are of similar near non-existant value.
Delusions of grandeur run rampant in this "Baloney" thread.
Happy delusions,
Vitality
The general stance is that weekend beta environments with a high load generally increase the variance in combat fluidity and impact delay.
Whether you're a shill, a reverse-shill, or a neutral I'm sure you can all agree on the above statement. Furthermore I'm sure you can all agree that this is an issue that has caused games in the past to become disasters.
No game "Should" sacrifice fluidity for gated animations. It's the same discussion the COD boys are having over the knife animations delaying their game to the point where they particularly avoid knifing.
But in our case, we'll just particularly avoid the game if it gets that bad.
"Mileage may vary" is just as good of an opinion as "Can't be sure til next weekend"
Both points are of similar near non-existant value.
Delusions of grandeur run rampant in this "Baloney" thread.
Happy delusions,
Vitality
So my concern is , (and I've bought it already and am playing at least a months worth ) , who's to say it still won't be shit at launch as far as the combat responsiveness and lag go when the real load is there and not a small subset like the currently closed beta is.
I'd like to see before launch a weekend where it's on the same patch level as the smaller closed beta and let's answer the overall question of how will the shit really work. Eliminates any excuses on either side.
I'd like to see before launch a weekend where it's on the same patch level as the smaller closed beta and let's answer the overall question of how will the shit really work. Eliminates any excuses on either side.
I didn't play Rift so I don't know if their rifts were like either of these, but Dark Anchors are events that occur at static locations and are meant for a solid 3 or 4-person group; the new Dark Fissures occur randomly in different locations and are meant for only a couple of people.You can catch a bit of footage of both here.
Utnayan
F16 patrolling Rajaah until he plays DS3
- 16,526
- 12,567
Ok so now the personal vendetta makes sense. Thank you for sharing that last bit of information.
Let's discuss those combat changes. .18 improved line of sight issues for abilities to not be exploited around objects as they had been in the past. (Meaning your NPC could be behind a brick wall sometimes, and you would still hit the mob for damage) It had nothing to do with the combat issues surrounding the responsiveness and tab targeting of NPC's and alt target switching. Line of sight has absolutely nothing to do with the combat issues and tab targeting issues because it was never a line of sight issue to begin with. It is an issue hampered by having two combat systems layered on top of each other. 1) An MMORPG point and click system that will automatically fire at one particular NPC once the player has engaged and tab targets that mob. 2) An action layer where you have a reticule combat targeting system. The two, frankly, conflict. The system itself is broken. What is happening is the two systems battle each other for control, causing immense amounts of broken in this specific scenario. The action system gets confused when you tabbed, and when you switch half way through (Which you will) the reticule system tries to take over, conflicts with the tab target switch, and the shot hits the ground, hits another mob, hits a tree... no one knows what could happen because the system breaks.
So far we have seen some posts from you detailing the fixes. One post indicated that combat wasn't an issue for most folks. Another post indicated that closed beta testing feedback was at a peak complaining about combat issues until January but now is better due to .171. I posted a link to Matt Firor's interview that said thanks to tester feedback, combat was now mostly positive. In August 2013. That contradicts what you said about beta feedback being negative in December 2013. Now you are saying that the line of sight patch, which fixed object line of sight and abilities firing through them at NPC's, fixes the 2 layered combat system that caused this in the first place. What it fixed was I couldn't hit my crab if the NPC was on the other side of a tree.
I can see how some people can get used to the combat system, I can see how one person even said they would play a game from 2006 to get used to a 2014 combat system just so they could play TESO. (Well, that one is pretty weird). But you are failing to acknowledge an objectively broken system.
As Draegan said, everyone will try it out for themselves. So maybe it might be best for you to talk about things that work in the game rather than contradict yourself over the combat system.
I am also interested in which other games you enjoy, because if you plan on staying in this community, I would imagine you didn't just come here to post about Elder Scrolls correct? You should visit the other games thread if you have more than just a PC and discuss some of the other games with us. What you like, dislike, what you play, don't play - some of your favorite designers, companies, etc.
Blackwulf
N00b
- 999
- 18
No, he said it was in .171 also. Just not collision detection.
Edit: I mean Rescorla when I say "he." I don't read Utnayan anymore.
Utnayan
F16 patrolling Rajaah until he plays DS3
- 16,526
- 12,567
The line of sight issues Rescorla just talked about (which s/he? said fixed the combat issues) wasn't in .171. It's in .18. They also don't fix the issues anyway so it's a mute point.
Players will see no changes in the weekend beta other than (hopefully for ZO's sake) a lot of improvements in bugs and queues. All the fixes rolled into the upcoming weekend beta were mostly megaserver fixes.
Abefroman
Naxxramas 1.0 Raider
- 12,594
- 11,937
So .171 fixes the issues that didn't exist except maybe less the 5% of the time and that nobody complained about anymore?
Tarrant
<Prior Amod>
- 15,801
- 9,212
rhinohelix
Dental Dammer
- 3,045
- 5,014
Point is, someone who isn't Rescorla who is also in the Closed Beta with the updated patches could go test this out right now, and come back here and tell us. We don't have to rely on him/her.
For me, the idea of lag is when I let go of the mouse button charging the attack, do the model's arm(s) start to swing. I had a terrible experience with that kind of lag during Friday/Sat and didn't notice it nearly as much Sun/Mon; it was hard to differentiate which kind of lag I was experiencing.
It is a shame that tomorrow we won't see this latest patch version but I am looking forward to crafting and going on from the starter zones for Dom and Daggers to see how those areas play as well. I am also going back to see if Melanie is there for that quest beyond ebonheart now.
- 26,236
- 39,960
My to do list for this weekend is to try the other two starting areas and see which one I like the best. Also like above poster, I want to fuck around a bit with crafting and get to know it a bit more. Also I want to try the PvP, as I did not get a chance to last time. I dont want to spoil any more of this game for release. Its bad enough to play through quest grid one time, but doing it twice is like double fucked.
Vitality
ＨＵＳＴＬＥ
- 5,808
- 30
Vitality
ＨＵＳＴＬＥ
- 5,808
- 30
Have you already tested all the character builds you're interested in?
Which build are you leaning towards?
Tarrant
<Prior Amod>
- 15,801
- 9,212
Do you? I mean we're all posting on an interest forum here, you realize that right?