If you're going to blow away all the work people did....

[Nakamuro Zataki]

Trekman, it is a question of time.

I do not (yet) know how to easilly move data between tables accross database boundaries.

[Phade]

a friend of mine works for a company that moves information between differing databases, its surprisingly complex and not somehting I'd expect Zat to do for free

think of it this way, we are not scritcly enforcing quota for the most part for the next 21 days.. (give or take based on starting day) and the xp you all had stored (myself included) is not going to be there so in essence you all still have your buffers..

It was not something we had any control over, I understand the frustration but not much we can do.

My 2 OH characters had well over 110% (I think?) when the database changed, and today they are both still at 110% + percent.

if you had a buffer set for a vacation time in the next 21 days please post it here or PM a manager, however since you don't really have to worry as much about quota till we get that 21 days of reporting done go ahead and take your vacatoin.

this isn't to say everyone can slack for 21 days cause you need ot show as passing after the 21 days is up.

[Trekman]

I believe the only fair solution for us uninvolved victims would have been to add an XP bonus of approximately the old surplus

I know it was wishful thinking, especially considering the pressure of time Zat had to get the page up and running. Don't get me wrong - I appreciate how fast Zat was able to revive his 6-months-old code.

That is why I said "would have been" and not "would be".

And I would not have liked the "numbers added back" to "feel better", but to ease the work ahead for both chain-members and -managers.

I admit my main concern was my own bonus and the "been honest for nothing" as described earlier, but it was not the only one.
At some point in time after the 21-day-"grace period" removal orders *will* occur, and some of them might be objected using the reset as justification.
Even if the chain managers can disprove that by juggling the various numbers, they have to deal with every single case which means additional workload.

Another reason for my post was more of a "philosophical outcry" - about how bad blood between two individual members can affect the whole clan of "uninvolved victims" (ok ok - "only" chain members this time).
Especially if "service providers" are involved.

[grimly fiendish]

instead of switching ppls exact amount of exp why not just make it across the board everyone gets say 50 mill and meery xmas

i know this is less than alot of ppl had but it might just be enough to make things workable for some ppl who dont have as much time to get back in

[Nakamuro Zataki]

Trek, after 3 weeks the buffer would be gone anyway, right?

Btw, the code has a config file (actually 3-4 of them), needed to change a couple of paths in other files also, but it was not that bad getting it up and running. Worst part was trying to find the old table structures.

However, transfering data between databases will require some kind of testing... No promisses, might look at it if I get bored. The thing is that extra caution is necessary, dont want to corrupt the newly uploaded data.

[Trekman]

Trek, after 3 weeks the buffer would be gone anyway, right?

Sort of. But that would imply that I made the surplus on one day (or very few days), and then no further XP at all. Then - after 3 weeks, my number would suddenly "be gone".
But in this case - I will not be absent for 3 weeks. I *will* play and add XP, but not much. Therefore "only" those XP would be gone that are the difference from what I produce today and what I produced the day 21 days ago.
Therefore the buffer would "fade away" slowly compared to a vacation where I am at the beach for 21 days without logging in....but obviously at some point it will be gone and I have to revert to "normal" XP production.

The effort and the risk to transfer data would have been justifiable if both sites would have used the same database layout by chance.
So *if* you get bored - do another movie

Grimly's suggestion of a "christmas gift" sounds interesting. It is Sunday, so I am too lazy now to think about implications on the chain and on the database

[Oof]

Good point on the implications on the database. Unless Zataki put a + 50 million calculation on the databases numbers, I would think the database would automatically reset to real numbers again once if read the raw data from an input. That is to say, I don't think he could simply add 50 million to everyone's XP because those numbers would differ from what the game sends in.

Sometimes I'm glad I'm not a database person.

[Trekman]

That is to say, I don't think he could simply add 50 million to everyone's XP because those numbers would differ from what the game sends in.

Oh well - Sunday or not :

Apparently the database is not only based on real input, or else no "reset to 0" would have happened when switching the sites.
So there is some kind of calculated number with at least one value *not* directly read from the uploads - which means that it ought to be possible to add either a fixed "gift" or a value read from the old database.

I do not know the ACStats-based calculations and databases. But from what I see in the Meginjarder XP Chain implementation I am not sure whether I *want* to know the ACStats version

[Nakamuro Zataki]

Trek, ofcourse something like that could be done. But the question is if adding 50M to everyone's credits is giving you something or if you will loose from it?

Then there is the time issue. I went out shopping and had coffee with a friend instead which makes this discussion kind of academic, but perhaps interesting anyway.

[Kitoko]

did we have a crash or something? or did we have to move again? this sort of explains my post as to why im now failing.

[Trekman]

I went out shopping and had coffee with a friend instead which makes this discussion kind of academic, but perhaps interesting anyway.

Of course it is academic