Michael Merrell

That is not consistent with what I've experienced with the Java version. Perhaps a mod was modifying that behavior.

Updates for my last set of notes:

Started two new survival games, but did not see any XP-related issues for at least the first 10 levels.

When I died, I lost all my levels, but kept my armor. So, that bug might not be related.

I didn't notice when, but in the new game that I've played the most, the XP bar got stuck at max, along with leveling on each orb. I noticed around level 70, and I'm not sure what level I had been before it started running uplease.

I tried knocking my levels down to see if thing returned to normal below a certain level. I was able to get as low as 7 with no change in the symptoms.

At one point, I allowed myself to die to see if that would zero my XP, but it did not. I retained the level I had at the time of that death.

I then threw myself into lava a few times to wear or my armor, and got down to level 7 repairing things with the anvil. The next time I swam in the lava I respawned back at level 37.

Also tried quitting and reloading, to no effect.

So, once it's broken it looks like it stays broken. I don't know if it had to do with the source of the orbs at the time (breeding cattle) or if it's happening to everyone at a certain point.

I'm not sure I follow. (Per the blog post) Isn't .7 build 4? Sure, there are the disconnects between the semantic and nominal versioning, but this issue is referencing the string displayed, which matches neither. I think it say "alpha", too.

This doesn't affect game play, but probably makes your job more difficult when sorting out which number was referenced when creating an issue.

I'll reword it to focus on the problem described, first.

The potential fixes could be deemed feature requests, which are often tracked in issue-tracking systems, but the core issue of poor information display in the anvil UI is either a code defect bug (if that information is supposed to be displayed, but is not) or a design/usability bug (because it causes significant issues for the user).

So, if you want to resolve it as by-design or won't-fix, I can understand, but invalid implies that it doesn't describe an issue with the product.

My observations:

On 0.15.90.7
NVIDIA Shield Tablet (touch) and Shield TV (controller)
Android 6.0.1

XP is dorked.

• XP bar remains full after next level is reached.

  • If XP is tracked as amount to next level, and not as a total value, then this value is not getting zeroed when gaining a level.

  • If scaling of XP required per level flattens at some point (i.e. doubles each level until level N, and then remains constant), the issue would be less obvious when required XP is scaling (only the XP requirement delta between the previous and next level would be required, but that's still more than 0). This would likely manifest as the experience bar remaining partially filled (e.g. 50% if each level requires 2 X the XP as the previous).

  • Might indicate that some code is using a cumulative XP value, while other code is reading the same value as XP towards next level. This might explain the irregularities in levels lost upon death. (i.e. formulas expecting a delta value are instead getting a total value.)

• Any XP gained adds levels.

• (sorry) Do not recall if this was a level per gain of XP (per orb) or level per XP point gained.

• I am not sure at what level this starts (I don't think it starts out this way)

• I died with 300+ levels, respawned with 235, died a few more times without going below 235, and noticed the issue much later, ~425. I'm now in the 700-800 range because of this issue.

• Used the anvil a few times, enchanting table only once or twice. Not sure whether the issue was present or changed around those uses. Both of these blocks remove levels in the expected manner.