dir|^|Packages
file|^|Packages/modification.mod|^|1549|^|1035502640
<file>
Sources/Packages.php
</file>

<search>
  $file2 = $file;
</search>

<replace>
//  Deleted by PacManFix Mod
</replace>

<search>
  while(preg_match("/<(id|version|author|email|homepage|info|approved)>\n(.+?)\n<\\/\\1>/is", $file2, $regs))
</search>

<replace>
  while(preg_match("/<(id|version|author|email|homepage|info|mod info|approved)>\n(.+?)\n<\\/\\1>/is", $file, $regs))
</replace>

<search>
  if($info['info'] != "")        echo "\n<br>$txt[pacman7]: $info[info]\n";
</search>

<before>
  if(($info['mod info'] != "") && ($info['info'] == ""))       $info[info] = $info['mod info'];
</before>

<search>
    $file = str_replace("<$regs[1]>\n$regs[2]\n</$regs[1]>", "", $file);
</search>

<replace>
    $searchloc = strpos($file, "<$regs[1]>\n$regs[2]\n</$regs[1]>");
    $searchlen = strlen("<$regs[1]>\n$regs[2]\n</$regs[1]>");
    $file = substr_replace($file, "", $searchloc, $searchlen);
</replace>

<search>
(file|search|add|replace|before)
</search>

<replace>
(file|edit file|search|search for|add|add after|replace|before|add before)
</replace>

<search>
if($regs[1] == "file")
</search>

<replace>
if(($regs[1] == "file") || ($regs[1] == "edit file"))
</replace>

<search>
if($regs[1] == "search")
</search>

<replace>
if(($regs[1] == "search") || ($regs[1] == "search for"))
</replace>

<search>
if($regs[1] == "add")
</search>

<replace>
if(($regs[1] == "add") || ($regs[1] == "add after"))
</replace>

<search>
if($regs[1] == "before")
</search>

<replace>
if(($regs[1] == "before") || ($regs[1] == "add before"))
</replace>file|^|Packages/modification.txt|^|1401|^|1035503089
Even though there are some issues with the Package Manager (PacMan) that need a 
serious rework of the system, there are a few minor issues that can be dealt with 
now.  This mod makes a few changes to the Packages.php file to fix two of them.

1) There is a bug that sent PacMan into an endless loop if you tried to use 
    some of the Mod Info Tags.  With this mod you will now be able to use 
    the <id|version|author|email|homepage|info|approved> tags.

2) There is a bug in the Mod Parser that when your mod file has more than 
    one [block] that is exactly the same, they would all get removed when it 
    reached the first one.  Example: your mod file has a search block for 
    "Some random text"  but you need to search in two different files.  After 
    the parser takes care of the first one, it removes that block from its memory, 
    but it removes all of them.  So when you hit the next file, that search block
    is not there.  With this mod you will be able to do that.

It also makes it possible to use a BoardMod.mod file in a YaBBpak.  Rather than 
you needing to convert the BoardMod tags to PacMan tags, PacMan will understand 
them as if they were native PacMan tags.  Just rename the "BoardMod.mod" file to 
"modification.mod" and use it as a PacMan mod file.  If a BoardMod package uses
a .php file to make database changes, it may still need to be translated.

-Jack