Yea well your useless trolling isn't doing anything but pissing people off so stop. Your reply below me just further proves your trollish nature.
Edited, Aug 18th 2013 2:47pm by Mopdaddy
·English·Theme
- Forums
- Final Fantasy XIV
- General Discussion
- P4 progress taken over?
P4 progress taken over?Follow
Mopdaddy wrote:
Yea well your useless trolling isn't doing anything but pissing people off so stop.
Suggest you learn what trolling is. And if you think it is, report the post and let Wint sort it out. Bet you I'm still here when it's said and done.
Drulian, Pie Eating Champion wrote:
Nashred wrote:
Drulian, Pie Eating Champion wrote:
Nashred wrote:
It is allot if not a majority.. Just look at the thread SE posted where you put you name and server.. The thread is 720 pages long and has 10 to11 replies per page that is 7200 + and It is adding several pages a minute since going up. This is only people that know about the thread and actually reported it too.
Edit just while posting this it jumped to 1001 pages that over 10,000 people.
Edited, Aug 18th 2013 2:26pm by Nashred
[quote]I know the thread and unless it's been purged a lot of those people are posting multiple times complaining that it had been 30 seconds or longer and not fixed. So I'll take that with a grain of salt...
Actually looking at it it aint what you are saying it is mainly post with people actually giving server and name.. there might be some double post but now it is 1097 pages long...
Google the error it is everywhere on every gaming site. This is no little problem right now.. If it was it would have been fixed hours ago...
Edited, Aug 18th 2013 2:33pm by Nashred
Ok simple math. 1097 pages, x10 posts a page = 10970 people affected if they are all legit posts and not trolls from other mmo companies (It's happened before)
Press release stating 150,000 concurrent login's during beta.
10970/150000= 7.3%
Still not a majority.
Well it is now growing 10 pages A minute. So we will see.. Probably most have not reported the problem and the problem is obviously growing.
My friend just got booted with the error so we will see when beta is over..
FFXI: Nashred
Server: Phoenix
FFXIV : Sir Nashred
server: Ultros
Server: Phoenix
FFXIV : Sir Nashred
server: Ultros
Drulian, Pie Eating Champion wrote:
Nashred wrote:
Drulian, Pie Eating Champion wrote:
Nashred wrote:
It is allot if not a majority.. Just look at the thread SE posted where you put you name and server.. The thread is 720 pages long and has 10 to11 replies per page that is 7200 + and It is adding several pages a minute since going up. This is only people that know about the thread and actually reported it too.
Edit just while posting this it jumped to 1001 pages that over 10,000 people.
Edited, Aug 18th 2013 2:26pm by Nashred
[quote]I know the thread and unless it's been purged a lot of those people are posting multiple times complaining that it had been 30 seconds or longer and not fixed. So I'll take that with a grain of salt...
Actually looking at it it aint what you are saying it is mainly post with people actually giving server and name.. there might be some double post but now it is 1097 pages long...
Google the error it is everywhere on every gaming site. This is no little problem right now.. If it was it would have been fixed hours ago...
Edited, Aug 18th 2013 2:33pm by Nashred
Ok simple math. 1097 pages, x10 posts a page = 10970 people affected if they are all legit posts and not trolls from other mmo companies (It's happened before)
Press release stating 150,000 concurrent login's during beta.
10970/150000= 7.3%
Still not a majority.
Generic math time?
13 people in my guild. 1 of us can still play.
13-1 = 12.
Of those 12, I am the only one who posted on that thread.
So let's make a stupid generalization and say 1 out of every 12 players who got the error actually posted on that thread. Let's not even worry about those who DON'T know how or don't care to report it.
So let's inflate the reported number times 12 to reflect actual affected accounts.
10970 x12 = 131,640.
131,640/150,000 = 87%. Aka The majority.
When in reality, all you would need would be 1/7 players who it's affected to still be the "majority", which is actually a pretty plausible scenario.
JP servers should also be not included, as they seem just fine.
Bottom line, it very well could be the majority. And it seems like it is.
Edit: Not to fail to mention that /r/ffxiv traffic increased by 75,000 hits when the majority of this started going down. http://imgur.com/GH4vnAg
But yeah. You're right. It's probably only ~10%.
~_~
Edited, Aug 18th 2013 12:03pm by FlixEffect
Edited, Aug 18th 2013 12:10pm by FlixEffect
Scholar
25 posts
Considering the level cap that was placed on characters, I think that the team is VERY Reluctant to broach the idea of a wipe. I believe that the level 20 cap was put in place, so that WHEN people found XP glitches, they couldn't be used to max out a character and endanger (i.e.: **** off all users) everyone's progress to date. Therefore, the level cap was really a failsafe to ensure that no wipe was necessary.
Of course, this doesn't broach the issue of gil and a possible gil exploit, but that is likely to be something that they could just deal with through a banning spree.
Of course, this doesn't broach the issue of gil and a possible gil exploit, but that is likely to be something that they could just deal with through a banning spree.
Ridinger wrote:
Considering the level cap that was placed on characters, I think that the team is VERY Reluctant to broach the idea of a wipe. I believe that the level 20 cap was put in place, so that WHEN people found XP glitches, they couldn't be used to max out a character and endanger (i.e.: **** off all users) everyone's progress to date. Therefore, the level cap was really a failsafe to ensure that no wipe was necessary.
Of course, this doesn't broach the issue of gil and a possible gil exploit, but that is likely to be something that they could just deal with through a banning spree.
Of course, this doesn't broach the issue of gil and a possible gil exploit, but that is likely to be something that they could just deal with through a banning spree.
You could also spin it to say that the level cap was put in so if there WAS a wipe, they could say "it's only 20 levels".
Would suck for those of us that got 3+ jobs at or near 20, though.
My girlfriend is still playing and there are still people but nothing like yesterday.. She is level 20 though and in some of the higher areas.
My point is this is no little problem even if it is only like 15 percent that a major amount of players. I would guess this is allot higher than 15 percent though.
If companies start too think 15 percent is a minority then that is bad.
What is funny is we both logged out the same time the same way on the same internet connection.. She got in today and I didnt..
She is on ps3 and I am pc... anyone on a ps3 get blocked ?
Edited, Aug 18th 2013 3:12pm by Nashred
My point is this is no little problem even if it is only like 15 percent that a major amount of players. I would guess this is allot higher than 15 percent though.
If companies start too think 15 percent is a minority then that is bad.
What is funny is we both logged out the same time the same way on the same internet connection.. She got in today and I didnt..
She is on ps3 and I am pc... anyone on a ps3 get blocked ?
Edited, Aug 18th 2013 3:12pm by Nashred
FFXI: Nashred
Server: Phoenix
FFXIV : Sir Nashred
server: Ultros
Server: Phoenix
FFXIV : Sir Nashred
server: Ultros
Guess math has changed in the 20 years since I graduated high school... back then it had to be greater than 50% to be a majority.
Not saying that it isn't a huge issue the week before launch. I'm just sick of seeing "90%+!!" numbers thrown around when if that was the case the servers would be ghost towns other than the "Afk ghosts" if characters are truly left logged in. This also isn't to most people a "major game changing bug" required for a beta wipe. No one is getting gobs of bonus xp or gil due to a programming glitch. Just a "DC doesn't disconnect you bug" that might be a stupid as a decimal point off in the "If player disconnects, kick off server after x time" line of code (I know that's now how it works, but you get my point) SE does need to issue an statement and apology on the whole matter and save face going into launch though. Maybe I'm on a server that's less affected by the bug than other's, who knows.
Not saying that it isn't a huge issue the week before launch. I'm just sick of seeing "90%+!!" numbers thrown around when if that was the case the servers would be ghost towns other than the "Afk ghosts" if characters are truly left logged in. This also isn't to most people a "major game changing bug" required for a beta wipe. No one is getting gobs of bonus xp or gil due to a programming glitch. Just a "DC doesn't disconnect you bug" that might be a stupid as a decimal point off in the "If player disconnects, kick off server after x time" line of code (I know that's now how it works, but you get my point) SE does need to issue an statement and apology on the whole matter and save face going into launch though. Maybe I'm on a server that's less affected by the bug than other's, who knows.
Yea I am on PS3 3102 and 90000 doesn't discriminate ;)
Ehllfire wrote:
TirithRR wrote:
Ehllfire wrote:
PhoenixOmbre wrote:
It would take a major problem for them to wipe the characters. Like the major problem we have now with error 3102. Just kidding!
Unless there is something game-breaking, for example a massive exploit to level or get rich, I think we can safely assume there will be no wipe.
Unless there is something game-breaking, for example a massive exploit to level or get rich, I think we can safely assume there will be no wipe.
3102 IS gamebreaking.
Character breaking and game breaking are two different things. The only way I can see 3102 requiring a P4 wipe is if for some reason the only way to correct the problem was to delete the characters.
The problem has been around for 48 hours with no word of fix, Id expect wipe. And it is gamebreaking if YOU CANT PLAY AT ALL DUE TO 3102. How hard is it to understand? THE WHOLE GAME IS BORKED FOR US
Edited, Aug 18th 2013 1:27pm by Ehllfire
BORKED!
Edited, Aug 18th 2013 3:14pm by supermegazeke
Drulian, Pie Eating Champion wrote:
Guess math has changed in the 20 years since I graduated high school... back then it had to be greater than 50% to be a majority.
Not saying that it isn't a huge issue the week before launch. I'm just sick of seeing "90%+!!" numbers thrown around when if that was the case the servers would be ghost towns other than the "Afk ghosts" if characters are truly left logged in. This also isn't to most people a "major game changing bug" required for a beta wipe. No one is getting gobs of bonus xp or gil due to a programming glitch. Just a "DC doesn't disconnect you bug" that might be a stupid as a decimal point off in the "If player disconnects, kick off server after x time" line of code (I know that's now how it works, but you get my point) SE does need to issue an statement and apology on the whole matter and save face going into launch though. Maybe I'm on a server that's less affected by the bug than other's, who knows.
Not saying that it isn't a huge issue the week before launch. I'm just sick of seeing "90%+!!" numbers thrown around when if that was the case the servers would be ghost towns other than the "Afk ghosts" if characters are truly left logged in. This also isn't to most people a "major game changing bug" required for a beta wipe. No one is getting gobs of bonus xp or gil due to a programming glitch. Just a "DC doesn't disconnect you bug" that might be a stupid as a decimal point off in the "If player disconnects, kick off server after x time" line of code (I know that's now how it works, but you get my point) SE does need to issue an statement and apology on the whole matter and save face going into launch though. Maybe I'm on a server that's less affected by the bug than other's, who knows.
That was the point of my post. You tried to throw that 10,000 out as a concrete number, and I showed how I could use my LS numbers to make it be the majority. Doesn't make sense does it? No, because no one knows the actual ******* numbers. But anyone who has even the slightest ability to think rationally and logically could pretty well establish that there's a decent chance the "majority" of players are having this issue.
The rest of that I agree with, I just wanted to make an example of how people shouldn't be throwing around numbers. And it could be very server dependent, I've sene screenshots where starter zones are literal ghost towns, my 1 LS mate who is in posted a picture with three people around the main city quest giver. An area that normall has 50+.
Math is fun! 100% of my household cannot play. However, 100% is still gonna buy/subscribe to the game. But let's not tell SE that. They need to sweat a little and fix that fast.
Nuit Midril - White Mage/Scholar on Ultros
Nuit the Insane! - Retired Druid on Sentinels.
Ombre - Retired Dragoon/bard on Phoenix.
FlixEffect wrote:
Drulian, Pie Eating Champion wrote:
Guess math has changed in the 20 years since I graduated high school... back then it had to be greater than 50% to be a majority.
Not saying that it isn't a huge issue the week before launch. I'm just sick of seeing "90%+!!" numbers thrown around when if that was the case the servers would be ghost towns other than the "Afk ghosts" if characters are truly left logged in. This also isn't to most people a "major game changing bug" required for a beta wipe. No one is getting gobs of bonus xp or gil due to a programming glitch. Just a "DC doesn't disconnect you bug" that might be a stupid as a decimal point off in the "If player disconnects, kick off server after x time" line of code (I know that's now how it works, but you get my point) SE does need to issue an statement and apology on the whole matter and save face going into launch though. Maybe I'm on a server that's less affected by the bug than other's, who knows.
Not saying that it isn't a huge issue the week before launch. I'm just sick of seeing "90%+!!" numbers thrown around when if that was the case the servers would be ghost towns other than the "Afk ghosts" if characters are truly left logged in. This also isn't to most people a "major game changing bug" required for a beta wipe. No one is getting gobs of bonus xp or gil due to a programming glitch. Just a "DC doesn't disconnect you bug" that might be a stupid as a decimal point off in the "If player disconnects, kick off server after x time" line of code (I know that's now how it works, but you get my point) SE does need to issue an statement and apology on the whole matter and save face going into launch though. Maybe I'm on a server that's less affected by the bug than other's, who knows.
That was the point of my post. You tried to throw that 10,000 out as a concrete number, and I showed how I could use my LS numbers to make it be the majority. Doesn't make sense does it? No, because no one knows the actual @#%^ing numbers. But anyone who has even the slightest ability to think rationally and logically could pretty well establish that there's a decent chance the "majority" of players are having this issue.
The rest of that I agree with, I just wanted to make an example of how people shouldn't be throwing around numbers. And it could be very server dependent, I've sene screenshots where starter zones are literal ghost towns, my 1 LS mate who is in posted a picture with three people around the main city quest giver. An area that normall has 50+.
Last I checked 80%ish of my LS was still logging on/or playing this morning. So unless it's changed I'm starting to think it IS server based and I got lucky, or we're the luckiest LS on the server
Catwho made a good post trying to possibly explain it in the other thread, how the 90000 error relates to the 3102 or whatever error, maybe the lobby server isn't double checking to see if you ARE still logged in which is why you get kicked with 90000 (loose connection) followed by the "Still logged in" error. Can't believe they haven't thought of it and at least rebooted the lobby server to try something.Drulian, Pie Eating Champion wrote:
Last I checked 80%ish of my LS was still logging on/or playing this morning. So unless it's changed I'm starting to think it IS server based and I got lucky, or we're the luckiest LS on the server
Catwho made a good post trying to possibly explain it in the other thread, how the 90000 error relates to the 3102 or whatever error, maybe the lobby server isn't double checking to see if you ARE still logged in which is why you get kicked with 90000 (loose connection) followed by the "Still logged in" error. Can't believe they haven't thought of it and at least rebooted the lobby server to try something.I'm on Behemoth, which I'm seeing tossed around a lot. We were also one of the servers that full on crashed Friday night. The weird thing is that I can't make a new character on a new NA/EU server (Phoenix), but I can make all the characters in want on the JP servers.
Same server, LL area is only place I've been other than brief trips for story line to other two nations. See that points to the servers not telling the lobby server you haven't logged off yet, which is what people are starting to point to more and more. Reboot the lobby server, let people stuck with bug log back on and figure out why it's not working correctly.
JP servers work but NA/EU servers are faulty! I since collusion!
Drulian, Pie Eating Champion wrote:
Same server, LL area is only place I've been other than brief trips for story line to other two nations. See that points to the servers not telling the lobby server you haven't logged off yet, which is what people are starting to point to more and more. Reboot the lobby server, let people stuck with bug log back on and figure out why it's not working correctly.
Hmm his posted pic was from the Gridania Inn area. I can't even imagine SE HQ right now. What a ************ While I'm sad I can't play, this is becoming all too amusing.
On the report thread on SE forums, literally when you click "Last Page", by the time it loads, there are 3-4 more pages. Probably 20 more pages by the time I'm done typing this. sh*t is nuts, hahah.
Edit: Went from 1353 pages when I typed this, now 1364 *pages* when I looked back.
Edited, Aug 18th 2013 12:52pm by FlixEffect
Edit: Went from 1353 pages when I typed this, now 1364 *pages* when I looked back.
Edited, Aug 18th 2013 12:52pm by FlixEffect
Wife just called to state the queue system at least for Behemoth isn't working, just says server is full try again later instead of the normal "28 people ahead of you" Do you wish to cancel screen we had last evening. Seems to be more and more issues popping up on the NA/EU servers.
I don't know anything about this stuff, but couldn't they feasibly just flip a switch and turn everything off? Like, full on power down everything. Then turn it all back on. You know like they do in IT. xD
Or is that what they did already?
Or is that what they did already?
I'm not sure of any reboots done at this point in time. Other than forced server crashes. And the more people poke around it sounds like maybe just the lobby server needs rebooted which can't take that long I wouldn't think... but I'm not a IT wiz.
Keep it civil folks, both sides.
Yes it's a big problem, and if you think SE Isn't doing anything about it then I don't think you're being realistic. A knee-jerk quick fix wouldn't help anyone though. They need to analyze the problem and make sure they don't break something else. My only concern is them getting it fixed before beta ends, if the beta ends before a fix it will be difficult to know if it resolved all issues.
Yes it's a big problem, and if you think SE Isn't doing anything about it then I don't think you're being realistic. A knee-jerk quick fix wouldn't help anyone though. They need to analyze the problem and make sure they don't break something else. My only concern is them getting it fixed before beta ends, if the beta ends before a fix it will be difficult to know if it resolved all issues.
Not certain this is the 3102 error, but this is on the beta forums:
Quote:
We are currently experiencing technical difficulties wherein some cases players are unable to log into certain Worlds in FINAL FANTASY XIV: A Realm Reborn.
The issue is being addressed, and new updates will follow as additional information becomes available.
We apologise for any inconvenience this may cause.
[Date & Time]
From Aug. 18, 2013 4:17 (GMT)
[Details]
Unable to log into certain Worlds in FINAL FANTASY XIV: A Realm Reborn.
[Affected Service]
-Moogle World
-Odin World
-Shiva World
-Cerberus World
-Faerie World
-Coeurl World
-Exodus World
-Diabolos World
-Adamantoise World
-Ultros World
-Midgardsormr World
-Malboro World
-Goblin World
-Cactuar World
-Gilgamesh World
-Leviathan World
-Behemoth World
-Balmung World
-Ragnarok World
-Sargatanas World
-Excalibur World
-Hyperion World
The issue is being addressed, and new updates will follow as additional information becomes available.
We apologise for any inconvenience this may cause.
[Date & Time]
From Aug. 18, 2013 4:17 (GMT)
[Details]
Unable to log into certain Worlds in FINAL FANTASY XIV: A Realm Reborn.
[Affected Service]
-Moogle World
-Odin World
-Shiva World
-Cerberus World
-Faerie World
-Coeurl World
-Exodus World
-Diabolos World
-Adamantoise World
-Ultros World
-Midgardsormr World
-Malboro World
-Goblin World
-Cactuar World
-Gilgamesh World
-Leviathan World
-Behemoth World
-Balmung World
-Ragnarok World
-Sargatanas World
-Excalibur World
-Hyperion World
#50REDACTED,
Posted: Aug 18 2013 at 2:26 PM, Rating: Sub-Default, (Expand Post) Anyone seeing flashbacks of 1.0's launch?
1445 pages as of last reload.
At this rate, there will be 20,000 reported outages and goodness knows how many unreported ones before beta is over. Jeeeeeeez.
At this rate, there will be 20,000 reported outages and goodness knows how many unreported ones before beta is over. Jeeeeeeez.
Recent Visitors: 236
All times are in CST
Anonymous Guests (236)
- Forums
- Final Fantasy XIV
- General Discussion
- P4 progress taken over?
© 2024 Fanbyte LLC