PDA

View Full Version : Lazines



Metsuro
02-19-2011, 04:50 PM
I'm extremely disappointed right now by this claim the best solution is to wipe. Its never the best solution to wipe. What happens when the game launches and after a month the DB starts corrupting... Oops wipe again?

Right now your just being lazy, and using poor judgement. This was suppose to be a "preorder launch" Yet... your still treating it like a full beta? Its time to face the facts here guys its to late. Your showing us this is how you'll handle it when its live. Its poor form.

If you guys really cant do anything but wipe, please for the love of god show us the schema your using for your DB so we make it so you only have to dump the tribes and totem data. There is no point characters should be effected by this at all. Its really poor design if thats whats its coming to.

Meanstreak
02-19-2011, 04:55 PM
Right now your just being lazy, and using poor judgement.

And you're a whiny ass.

You are not the developer. You do not have access to their server files. You can not see the full extent of the problem. They can. I'm sure they didn't want to wipe again, knowing how disappointed we would be. But if they have to wipe, which they said they would only do if it was required, then that's fine with me.

FabricSoftener
02-19-2011, 04:57 PM
... please for the love of god show us the schema your using for your DB so we ...

lol

Metsuro
02-19-2011, 04:58 PM
and you're a whiny ass.

No, I spent 24 hours yesterday sitting on my spot to mention it. Im not being whiny, those being for a wipe because they only stuck around for an hour and left are being whining.

Learn to insult better <3.

Celstra
02-19-2011, 04:59 PM
So your saying instead of a quick wipe we should wait weeks? Or however long it takes to sort all the data out.. Guess that makes since o.o

Ziggy
02-19-2011, 05:01 PM
Yes, the 3 people making this game are real lazy. I mean Jooky could just stop time so he can go through the database and fix it so we don't lose what amounts to 2 hours of actual in game progress.

wirerzo
02-19-2011, 05:03 PM
I shouldn't even bother responding to this thread. But I did, oh well.

Grow up.

yoori
02-19-2011, 05:03 PM
DB isn't corupted, DATA is. There is a difference. DB is tables and refferences between them. There must be something in the code that was saving bad data into db and they are fixing it.

But at this point it's better to wipe and start over. Lots of tribes lost their lands to other tribes due to server rollback(saving corrupted data). How do you decide which tribe should get that land?

Sure it easier and probably can be fixed without wipe but is it fair?

tilla
02-19-2011, 05:03 PM
Sorry Metsuro but you're wrong in this case. Jooky has fully explained what caused the DB problems and fix he is implementing which includes implementing a whole extra save system - no small feat! Laziness indeed!

Meanstreak
02-19-2011, 05:03 PM
You spent an entire 24 hours? Good job. Maybe you should get some sleep since it seems to be impacting your judgement. My tribe had to find a new spot because of the totem bug. After 9 hours of dealing with the lag while searching for a new spot, we finally found one. You're not alone or unique.

Jadzia
02-19-2011, 05:08 PM
Wipe is always the best solution for a corrupted database, as long as it is possible. I agree that it would be catastrophic if that happened some months after launch, but loosing half a day of work isn't so painful. I'm happy Jooky chose to wipe, facing random bugs all over the game because of corrupted data would be much much worse.

Metsuro
02-19-2011, 05:08 PM
So your saying instead of a quick wipe we should wait weeks? Or however long it takes to sort all the data out.. Guess that makes since o.o


Yes, the 3 people making this game are real lazy. I mean Jooky could just stop time so he can go through the database and fix it so we don't lose what amounts to 2 hours of actual in game progress.

If they have to go through every line of tribe and totem information they really did poorly design the DB.

Most modern DB have the ability to accept a single query to dump the entire tables of information. so you could do like an sql DB, DROP TABLE "Tribes". This then deletes all the information in those tables making them empty. One single line and the tribes were wiped.

Thats what I'm saying, if they design the schema or the structure of how the information is stored in a way that isn't going to be easy to just dump the tribes somethings wrong. If something like this happens during the live game do you think people are gonna put up with a wipe cause its the "easier" option?


DB isn't corupted, DATA is. There is a difference. DB is tables and refferences between them. There must be something in the code that was saving bad data into db and they are fixing it.

But at this point it's better to wipe and start over. Lots of tribes lost their lands to other tribes due to server rollback(saving corrupted data). How do you decide which tribe should get that land?

Sure it easier and probably can be fixed without wipe but is it fair?

A table is both the data and the entries to which I identify them. so The table of tribes, would could field for index name players size, and this table would contain an bit that says, 1, Epic, 5. This right here the information IN that entry is whats corrupted, so instead of Epic having the right index of 1, might have some how saved as 5. While the totem referencing it might for some reason have referenced a different tribe.

DB's arn't as hard or complicated to understand guys. Seriously grow up and learn something, stop just sitting there assuming you know whats best but thats what you were told...

Niburu
02-19-2011, 05:08 PM
If the data would be dmg in 2 weeks than they would upload the last working backup. This was not possible yet because the server crashed over and over. Sorry if you have no clue you shouldn't make angry threads

FabricSoftener
02-19-2011, 05:22 PM
DB isn't corupted, DATA is. There is a difference. DB is tables and refferences between them. There must be something in the code that was saving bad data into db and they are fixing it.

But at this point it's better to wipe and start over. Lots of tribes lost their lands to other tribes due to server rollback(saving corrupted data). How do you decide which tribe should get that land?

Sure it easier and probably can be fixed without wipe but is it fair?
Yeah its likely there are a ton of data where the realtionships dont exist because it wasnt able to save the data nor rollback the transaction. Something this massive it really does make sense to wipe because it could take a lot of work to fix those realtionships. Clearly if something like this happend on month 2 it would be a different story but if we dont wipe it would take a long time before he could go live again. I would rather he wipe and spend that time on new features.

Metsuro
02-19-2011, 05:26 PM
If the data would be dmg in 2 weeks than they would upload the last working backup. This was not possible yet because the server crashed over and over. Sorry if you have no clue you shouldn't make angry threads

And whats the promise on the back ups not being corrupted? What than? Man you cant just make a half assumption and jump on it. You have to plan these things out.

MrKrueak
02-19-2011, 05:26 PM
DB's arn't as hard or complicated to understand guys. Seriously grow up and learn something, stop just sitting there assuming you know whats best but thats what you were told...

maybe you are the one who needs to stop assuming, as the devs have said it is not only corrupted data but data wasn't even saved at times due to the server lagging out during the save process, some claimed lands only to find out it didn't save and someone else got it afterwards so whether the db can or can't be fixed giving the situation of what went on the only fair thing to do is to wipe and go from scratch again.

as far as this happening a gain they also are already implmenting a secondary db save feature to rectify this. I'm sure they also back up the data daily if not hourly but that would not have helped this time since there was no good data to begin with to backup.

Klecko
02-19-2011, 05:29 PM
I know ,nobody is happy with this weekend.But to call the team lazy that's just wrong.You can call them understaffed,but not lazy.
How many hours of sleep you think Jooky had since thursday,not many.What's going to happen when he tries to sleep tonight? he's going to see nothing but lines of code running by