You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seem to be issues with the memory system on the website:
First of all, even by defining a lot of variables, I'v always had my memory size at 0.
Also, before my first set-memory, *memory* would always return 0. I knew it was false thanks to the account function.
Moreover, it seems that the set-memory function calculates the difference in memory from *memory* instead of account allowance, as I've concluded from my first set-memory which made me pay for selling memory:
However, I couldn't reproduce this issue after that as my *memory* synchronized with my account allowance.
It also seems like the set-memory function sometimes forget to change the amount by 1, as shown by these two exemples:
However, I cannot see the logic behind the appearance of this issue
It is not linked to the amount set as seen here:
Nor it is linked to the amount changed:
We can see in the two screenshots above a small change not working, a big change working and a bigger change not working.
Furthermore, this also cause issues while transferring memory, with memory simply diseappearing into nothingness:
Side note: transferring convex coins, on the other hand, works perfectly fine
The text was updated successfully, but these errors were encountered:
Darkneew
changed the title
Memory size not well calculated/displayed
Issues with memory
Aug 2, 2022
There seem to be issues with the memory system on the website:
First of all, even by defining a lot of variables, I'v always had my memory size at 0.
Also, before my first set-memory, *memory* would always return 0. I knew it was false thanks to the account function.
Moreover, it seems that the set-memory function calculates the difference in memory from *memory* instead of account allowance, as I've concluded from my first set-memory which made me pay for selling memory:
However, I couldn't reproduce this issue after that as my *memory* synchronized with my account allowance.
It also seems like the set-memory function sometimes forget to change the amount by 1, as shown by these two exemples:
However, I cannot see the logic behind the appearance of this issue
It is not linked to the amount set as seen here:
Nor it is linked to the amount changed:
We can see in the two screenshots above a small change not working, a big change working and a bigger change not working.
Furthermore, this also cause issues while transferring memory, with memory simply diseappearing into nothingness:
Side note: transferring convex coins, on the other hand, works perfectly fine
The text was updated successfully, but these errors were encountered: