Inter-Level Experience Reset - A Possible Solution

Quote:

---

Originally Posted by Anonicat

You're not suggesting making a table row for for literally every experience point are you?.... then trying to join it... with other tables are you....

---

That’s precisely what I’m suggesting. A nonvolatile table with 325.8M rows, fully indexed and partitioned, will be incredibly performant for a join like this.

Quote:

---

Originally Posted by Krojack

IMO, resetting the experience bar back to 0% of the current level is an extremely small price to pay.

Even if I had a job at 90% though level 79 and it got reset to 0% I wouldn't care. It takes no time at all to get that level anyways. Hell, you can get little over half of that level being afk 70% of the time in an MSQ Roulette.

If people care that much then push all your jobs just over the line now and your loss will be almost nothing.

---

This is the actual answer, but this kind of reasonable response has no place on the internet.

Quote:

---

Originally Posted by Jpec07

That’s precisely what I’m suggesting. A nonvolatile table with 325.8M rows, fully indexed and partitioned, will be incredibly performant for a join like this.

---

No read my other response. That's too much. Why join a table that big.... there is still a performance hit. Just cause the algorithm for joins is optimal doesn't mean it won't take some time.

See my other response.

Quote:

---

Originally Posted by Equitable_Remedy

This is the actual answer, but this kind of reasonable response has no place on the internet.

---

Yes this is the actual responswe. But I felt like delving into CS stuff.

Pointless armchair developer suggestions.
Do you think any of this didn't occur to them? They've decided to do it this way for reasons you do not know.

You should know that it's unwise to propose a solution when you do not know the details of the problem.

Quote:

---

Originally Posted by LariaKirin

Pointless armchair developer suggestions.
Do you think any of this didn't occur to them? They've decided to do it this way for reasons you do not know.

You should know that it's unwise to propose a solution when you do not know the details of the problem.

---

I agree with you to some extent. And I'm just replying to OP's thoughts on it. Second stop with "Armchair X". First we've both worked in software development as a career, so we do have some knowledge on it.

Second you must be of the belief cause some one is a "Senior Software Engineer" as a job 40+ hours a week that they are an expert on said subject. Let me assure you job titles mean jack diddly in the real world. You couldn't be further from the truth my friend. Job titles are just titles to make oneself feel better very rarely do they mean what they should. Now im not saying the Devs at Square Enix are like this at all.. But some people do have actual knowledge in that field and have some insight into.

Also just a side teaser, you know those career professionals you speak so highly about they get hacked all the time by people who aren't employed by said companies. Check out Cyberpunk 2077, or any other. Kinda odd, didn't think those software professionals were able to be touched.. *shrugs*

I am experienced with database development, but I think no matter what your experience is, there is no way to tell what can be done without knowing the database architectures, the technical constraints that they have, the qa process they have, etc etc.

Just a guess, but they probably are trying to keep it simple to avoid having too long a downtime before EW release with too many things to check and verify post-release when XYZ player reports having only 20% of their progress now when they are certain they had 80% beforehand, etc. This is a safe way of doing things with a very, very considerable amount of advance notice.

Quote:

---

Originally Posted by Garnix

I am experienced with database development, but I think no matter what your experience is, there is no way to tell what can be done without knowing the database architectures, the technical constraints that they have, the qa process they have, etc etc.

---

True. Yes. But speaking in a more general sense. But do keep in mind Developers do make things more complicated than things need to be.