You probably don't want so complex scripts, none the less they perform two most wanted tasks once you're at cryptology and if you're getting deeper in it: the shuffling and the baits.
Since our cryptology style relies on Vigenere tables, luciferizing and baits are relevant: I do not go into more technicalities, but once found the cipher you can also find the guy with enough brains to decipher, also if it might take years (deciphering "Enigma", the nazi ciphering procedure, required years of focused efforts): the main threat to Vigenere Tables (since every cipher has a potential foe) is the so called "Babbage" analysis which could deduce part of the cipher analyzing the frequency of more recurrent letters: but if you do not only crypt, but you also:

Anyway, keep in mind: the difference between lucifer and cryptoBaits is (for both yield as a result a shuffling of the text) that lucifer shuffles the existing input text, as opposite to cryptoBaits which adds characters to it, and then invokes lucifer to shuffle the overall amount (original text plus baits, that is).

Away with the chatters, here are your scripts:

3. ARGUMENTS for LUCIFER:
   1. message is mandatory, is the text to shuffle
   2. keyword is optional but if you provide it is better!
   3. cryptDecrypt argument flags whether the script must shuffle or rebuild the ordered text: for no value or zero it shuffles, for value 1 or integer it rebuilds the original (provided the keywords match)
   4. alphabet must be a string (in between single quotes at least, that is, so that you can custom the chars that have to be recognized. Please do not include in your keywords chars which are not in the alphabet. Providing a different alphabet when shuffling demands that you pass the same alphabet also when re-ordering: in other words, passing an alphabet is like... providing a 3rd keyword which makes your crypt more and more cryptic... As for the ways you can use these features, we're currently (NOV 2001) preparing the ENDLESS TOKEN file, check our front page to see when it's online and ready.
   5. fragmentWidth argument is optional, and flags the width that each fragment should carry: shuffling a text means, in fact, fragmenting it into pieces and then rearrange these chips. The lower the better, since pieces of one char cause a complete shuffle. I suggest not to set the fragmentWidth, or to set it to 1. Moreover, if this width cannot divide the length of the message, it gets automatically decreased so after all setting it to 1 should be the wiser and safer move (also considering that would make no sense to shuffle chips 10 chars long, for instance, since shuffling is meant to prevent revealing symmetries to appear. It is pretty difficult that such symmetries could ever appear in this crypting system, but if you add also some lucifer and cryptoBaits you're even safer!)
   6. To run these scripts you need to have defined in within the same javascript source also the fragmentString function which can be found here - array7 file.
   7. Example, with basic arguments, for invoking this script:
      lucifer(message,myKeyword,0) to shuffle (all chars since no fragmentWidth has been specified),
      lucifer(message,myKeyword,1) to re-order.
   8. Eventually, to be honest I have a small doubt on the workings of this fragmentWidth argument, so my advice is to never set it (which defaults to 1) or set it to 1. Of course if you set it, anyway, when you decipher you have to be sure that keyword, alphabet, fragmentWidth arguments are all the same (and, obviously, also the text to work on is the right one...!).
   9. If you get starnge results, before arguing these scripts do not work, please consider that you may have inadvertantly crypted the crypt, or forget a keyword, or similar: these scripts do work!
4. WARNING & ARGUMENTS for CRYPTOBAITS
   1. When dealing with cryptoBaits and your input message is from a TEXTAREA, namely a form field which allows for new lines and carriage returns and tabs the script may be fooled. Instances:
      1. A new line char is what is at the end of a line, and is matched by a carriage return at the beginning of the next line: this means that in a new line there are nothing short but 2 (two) chars hidden to the human sight.
      2. At times these chars are treated like double chars, yielding as an eventual result 3 or 4! The script might be unable to process them properly, thus messing up the indexes for rebuilding a text: and messing up one index, means to mess up also all the subsequent ones. I repeat: a javaScript issue, not a script issue: simply, javaScript doesn't seem to provide programmers with strong enough tools and methods to force the recognition of escaped chars without stumbling into unpredictable mutliplications of them.
         If you use baits, try decrypting your own crypt before using or sending it. This applies only in case you use baits on/from textraea fields.
      3. You should not use or rely on cryptoBaits too much when crypting text from textarea fields.
   2. luciferFunc argument: I apologize but you have to set this always and to zero: it is a flag which, when cryptoBaits invokes lucifer (since it does) instructs lucifer to perform a certain task: if you omit it or do not set it to zero, the function would not work: I repeat do not omit it, just set it to zero: it has to exists someway since lucifer makes a reference through a statement which uses the caller.argument constructor (caller is a reference to a function that invokes the current function) and if the argument is not passed (even though as a zero!) the statement caller.arguments[x] would yield errors you see...! I put it as first argument, although not an intuitive or friendly position, just because I want you to be fully aware that you do have to define it somehow, even if as a ... zero!