I'm assuming that the $ maxenergy = energy bit of code is to refill your energy each day; if so, the variables are backwards. If you have the necklace and saw Daniel's last moments, before this update you'd be at 50 current energy and 250 max (since you used 200 to see the last moments). Which means this bit of code at the start of this update
sets max energy to 50, and then energy to 300. It also ends up erasing the +100 max energy you get from the memory fragment right before it.
It doesn't break anything (yet), but something to be aware of before writing any bits that require energy. Could fix it at the start of the next update with
I also just noticed that picking the option to not take the necklace will throw errors, since the if statements there use a single = instead of the == they should be.
Code:
if mysteriousnecklace == True:
$ maxenergy = energy
$ energy += 250
else:
$ maxenergy = energy
It doesn't break anything (yet), but something to be aware of before writing any bits that require energy. Could fix it at the start of the next update with
Code:
if mysteriousnecklace == True:
$ maxenergy = 250 #or 350? Not sure what it's actually supposed to be; it's orignally set to 100, then a "refill" sets it to 0, and then the necklace increases that by 250
else:
$ maxenergy = 100
if mp >= 8: #for the memory fragment
$ maxenergy += 100
$ energy = maxenergy
I also just noticed that picking the option to not take the necklace will throw errors, since the if statements there use a single = instead of the == they should be.