Alternatively, join us on Discord.
You can help CodeWalrus stay online by donating here.

AdventureWalrus! [CSE] [xlibC]

Started by Unicorn, April 04, 2015, 05:03:56 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

DJ Omnimaga

Oh, then if they don't change it's actually nice. Maybe @tr1p1ea could provide more info about this? I wonder if this could be used for some BASIC tricks such as shells or other things...


USERVARS are only really temporary storage to be used at runtime. I do suggest lists etc for more permanent storage.

Other users can indeed overwrite your data if they use the same USERVAR number, RAM clears i'm not completely sure about however other libs/shells/programs etc can overwrite the data as well.

DJ Omnimaga

Yeah I guess if another xLIBC game is ran after this one then this could definitively be an issue. It would definitively have been interesting if someone could have made some sort of BASIC file manager or something for practice that managed to keep its folder structure saved inside uservars and preserved after a RAM clear. I generally prefer lists anyway, although I guess on the CSE RAM is more limited.


Awesome, thanks for clarifying. I've  made a mistake in this programming progress, I haven't marked down all my variables. :$

Guess when I have time ill drop in in sourcecoder and look at all the variables.

??? ??? ??? ??? ???

DJ Omnimaga

Ouch. I tend to do that sometimes, but only for very small games that don't use many or if I am sure I'll finish the game in just a few weeks.

Powered by EzPortal