Post: Things NOT To Do In My XML Generator or ANY Mod Menu
04-30-2011, 01:47 AM #1
pcfreak30
>> PCFreak30.com Happy<<
(adsbygoogle = window.adsbygoogle || []).push({}); Ok first, I would wish for a mod to sticky this so it won't be piled in a day, as I plan to stop the repeat questions by those just joining us and those that won't listen..

If anyone has anything I should add, let me know.

So a few things you should NOT do in XML (my generator).


  • Do NOT attempt to put unlock or prestige codes as a menu, sub-menu, or menu item. They will NEVER WORK.

    Setplayerdata CAN NOT run in game and I have yet to find a work around.


  • Do not use the "&" symbol. It seems xml parsers (programs that read XML and process it) don't like the use of it. Just use the "and" word.
    Heres what I got when using the symbol:
        xmlParseEntityRef: no name
    


  • Do NOT use double quotes in XML. My generator auto adds that, so if you put then in yourself, you will break the syntax in the CFG.
  • Do not try using special characters in XML, as you can get weird errors from the parsing.


What NOT to do in a Mod Menu PERIOSad Awesome


  • Do NOT attempt to put unlock or prestige codes as a menu, sub-menu, or menu item. They will NEVER WORK.

    Setplayerdata CAN NOT run in game and I have yet to find a work around.

  • Do NOT use double quotes while setting a variable string, it breaks syntax. Example:
        
    set a "clantag "abcd" " <-- bad syntax on CFG even though this is not programming.




Hope this clears up any confusion..
(adsbygoogle = window.adsbygoogle || []).push({});

The following user thanked pcfreak30 for this useful post:

iExXoTiK
05-02-2011, 08:27 PM #11
-Brad-
Xbox is great
Is your Menu generator not working right now?
07-14-2011, 06:57 PM #12
how do you fix "StartTag: invalid element name"?
07-16-2011, 07:53 PM #13
You Should Put These Hints On Your Website Lol

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo