egghelp.org community

[Seka]

I am pretty sure I know how to write a variable to a line in a file. My goal here is to use an outside file to "record" the state of a variable, so that if the bot resets it doesn't forget what the variable was set to the last time it accessed the script.

Let me explain.

I need to increment the value of a variable, in order for the bot to know what change to make on which day, in the course of eleven days. I just realized that by initializing the variable the way I do in the script, that if the bot dies or resets the CONF, it will start the variable from scratch.

So, every time I increment the variable, I want to write the value to a file. Then, pull that value from that file, each time the bot needs it for the script. Thus, avoiding repeating the same action two or more days in a row.

What I need:

I can't quite figure out the code to set a variable to a line in a file, then after the variable is increased an increment, overwrite that file line with the new value.

I'd really appreciated some help with this!

Thank you.

[willyw]

There is some very helpful info on file operations, here:

http://forum.egghelp.org/viewtopic.php?t=6885


Probably more than what you need.... it sounds like you need to write only one line, with one number on it, to the file.

You might also find some useful info here:
http://www.tcl.tk/man/tcl8.5/TclCmd/open.htm#M7
or close to there.
http://www.tcl.tk/man/tcl8.5/TclCmd/open.htm


The main page is:
http://www.tcl.tk/man/tcl8.5/TclCmd/contents.htm

I hope this helps.

[nml375]

There are a few ways of doing this..
However, I'd probably settle with restoring the value when your eggdrop is restarted, rather than everytime the variable is read.

One of the simplest ways of doing this, is actually to have your code write a script that sets the value.. then all you need to do is add a "source restore.tcl" to your config-file

[Seka]

Thank you both for the quick responses. I was able to rig something together, using the documentation.

nml375,

It looks like what you're suggesting could significantly lower the amount of code in my primary script.

My question is this, though. If I need to increment the value of the variable and store it in several different scenarios, would I need to repeat that code snippet throughout the script?

Example:

[nml375]

The first problem with the code you posted, is that state is a local variable. The script-solution I mentioned "only" works with global variables (it could be made to work with local variables as well, but the hazzle really isn't worth it.. just use a global variable instead..)

Assuming we use a globalspace variable ::state instead; the posted code would only need one instance of the "save-code", provided that we add it at the end of the "example" proc, that we place the code at the end of the proc, and that we do not exit the proc prematurely (no return statements, etc).

[Seka]

Ok. So, here's what I've got. It is untested, so far.

Let me know if I need to change anything, please:

[nml375]

Please indent your code properly when posting, it makes spotting issues such as the extra } in your code that much easier to spot... not to mention reading the code.

First, since you named your variable rpday, not state, you'll have to change that in the save-code as well..
Also, if you go with the script-solution, you don't need to write the value to "restore"; I'd suggest you only use one or the other to avoid confusion, not both..

Also a hint, since you're building such many states on a single expression (variable), I'd considder using switch instead of those stacked if/elseif/else's...

Finally, as for reading the generated rpday.tcl upon startup; I'd use a catch-statement - just so I wouldn't have to bother making sure the file is always created (yes, I'm lazy). I'll even add a default value in case there was an error loading the file...

[Seka]

Looks like that is going to do it. I just need to format my topic a little better. I can't figure out how to keep the script from thinking that the brackets in the topic are code.

Thanks for your help, NML!

[nml375]

Escape them as \[ \]
_________________
NML_375, idling at #eggdrop@IrcNET

[Seka]

Awesome.

Solved.

Thanks again!

[Seka]

[nml375]

Sorry, seems I forgot to increase the value of rpday at the end of the proc.. I'll update my previous post to correct the issue in a sec..
_________________
NML_375, idling at #eggdrop@IrcNET