DecoderScript Reference
If you have the relevant background, it may be helpful to think of a decoder as the description of a large table in which each entry defines a field, a group, or a branch. The protocol analyzer traverses this table starting at the top, jumps around as instructed, and terminates when it meets an END_MAIN_PATH. If you lack experience with such languages, don't worry; it is absolutely not required!
Yet another way of looking at DecoderScript is as a statement language that controls the interface between the protocol analyzer and a set of methods that perform the nitty gritty of decoding.
We now describe each of these reference statements in turn.