Difference between revisions of "Import:AWarn2"
Jump to navigation
Jump to search
(Created page with "This article will lead you through the import process for AWarn2 *The warning admin will not be imported *Warnings will appear in GExtension as soon as the warned player conn...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | This article will lead you through the import process for AWarn2 | + | This article will lead you through the import process for AWarn2. |
*The warning admin will not be imported | *The warning admin will not be imported | ||
*Warnings will appear in GExtension as soon as the warned player connects to the server | *Warnings will appear in GExtension as soon as the warned player connects to the server | ||
*Warnings will not be imported twice | *Warnings will not be imported twice | ||
| + | *If you were using MySQL, the AWarn2 tables must be copied to the same database as GExtension. | ||
| − | Run this command | + | Run this command one the server or client: |
| − | + | ||
| + | '''gex_import_awarn2''' | ||
[[Category:Import]] | [[Category:Import]] | ||
Latest revision as of 13:49, 9 December 2017
This article will lead you through the import process for AWarn2.
- The warning admin will not be imported
- Warnings will appear in GExtension as soon as the warned player connects to the server
- Warnings will not be imported twice
- If you were using MySQL, the AWarn2 tables must be copied to the same database as GExtension.
Run this command one the server or client:
gex_import_awarn2
