I know some people think eval() is evil, but being able to evaluate a code string at runtime in VC would rock. In addition, it would also rock out a lot more than using GetInt() and SetInt() and CallFunction() excessively sometimes. Plus eval() would have the advantage of being able to interact with structs if done right. What do you guys say?

All the machinery for this is already in place - I actually had it implemented for a while, but removed it because I couldn't come up with a situation in which CallFunction() didn't suffice. But if we want it, it would be about 15 seconds' work.

EDIT: Well, no, not quite, Jesse. This is only true in non-releasemode. I forget what, but there's some reason the code editing (and evaluation) only works if we actually do the compilation. I'll investigate.