Why vBPhrases?
 

Lately I have been curious as to the advantages of the vBulletin phrase system as compared to vBulletin Options fields.

It seems to me that they ought to be interchangable (Although common sense prods me into thinking that they are not). Is there any reason to use one instead of the other aside from abiding by a set-standard? I suppose that there must be some significant difference. If someone could explain it, I would greatly appreciate it.

I personally find the vbphrase system to be rather un-userfriendly, and would prefer to use vbulletin's Options fields or a custom language system instead especially for one-word phrases closely linked with certain options.

Perhaps someone could offer me some tips/info/advice. Thanks!

(Additionally, what is the Syntax for using vbphrases within php files? I have not really looked into it, and it might save me some time if it becomes necessary to use that system.)

Edit: Just for clarification, I realize that Phrases allow the use of special variable replacements and syntax, ect. I am more interested about performance based differences, however.

Quick answer off the top of my head...

Performance-based Difference:

• call in only certain phrase groups per file to limit memory usage

Syntax of vB Phrases within PHP files:

• $vbphrase['phrase_varname']

How are options handled in comparison? I thought that all options available for calling on any vbulletin powered page?

Thanks for the syntax! :D (I shouldn't have had to ask.^_^)

the separation of settings/options from text. phrases were created to make translation of vbulletin and modifications that use the phrase system into any language. vb options should solely be used for settings only. using vb options instead of phrases is misuse of the system and would confuse others as to what you were doing. you are also adding tons of options to the vbulletin settings table which are loaded every page unlike a dedicated phrasegroup which is only loaded when requested.

Well what I would be doing is not fully phrasing the hack from within the settingsgroup but only providing certain phrases which were especially relavent to other (wholly legitimate) vbulletin settings.

Thanks for the information on the degree to which additional vbulletin options would affect performance. The difference would be (at the bare minimum) around 30 settings, so I assume that this would cause an unnecessary burden. I guess I will make a custom settings section then.