44 réponses à ce sujet

[dunahan_schwerterkueste_de]

When you use cmd, or the command console, first start Moneo with 'moneo'. Followed by ctrl+] and at least write help.
The xml file is used as a 'database' which everyone can edit/add. These corrections will be seen in the cmd/moneo-helpsys.
As far as I saw, only the RC3 supports it.

If you have a version like 4.0.2.24 (linked in Funkys first post) or earlier, you should download the RC3 I linked before. I found that file in a thread in this forum and thought it would be good to see it here too.
My, or better this version is 4.0.6.27rc3... I'm working on a sort of lexicon of it. Currently I am copying all of it's info's into this doc. It contains even Funkys thread. So I got a doc likely the nwscript lexicon... But it's not that usable now

[dunahan_schwerterkueste_de]

Something from the 27rc3:

What's new in build 27

Fixed:

Many syntax-level problems were resolved, especially for variables. A crash bug in for-loops over ERF resources was finally resolved.

Added:

Loads of additions: .names attribute, plus (et), minus, plussp (y), fileinfo, forcedirectories, system (execute shell commands), and Moneo's command mode (including the helpsys you're reading now). gff.add can now add Structs, and the syntax /^/ (parent of context) supplements /~/ (child of context).

Changed:

Warnings are now enabled by default. The bind operator =~ was changed to literal in, and completely deprecates %erf['resource'] syntax. + is much more strict about numeric addition. bic.vault option FullPaths renamed to NoFullPaths. filesys and system.system disabled by default.

[Proleric]

Thanks. I installed RC3, but regressed to Funky's tried-and-trusted 4.0.2.24.

I found the DOS help no easier to navigate than the raw XML. Also, RC3 clutters the working folder; maybe I should add Moneo to the DOS path, but my motto is "if it ain't bust, don't fix it".

Look forward to your user-friendly documentation, though!

[dunahan_schwerterkueste_de]

I wouldn't add it to the dos path, but you reduce the amount of files from RC3 to the exe itself. Meanwhile I'm running both versions under the same folder, only renamed

 

The document seem to be in a good shape. For the first version, I have to do some cosmetic thingies, before I'll link it here.

[dunahan_schwerterkueste_de]

Okay, some things I've noticed trying the RC3. If you call a for-loop for example for every *.git file in a opened module, the command/syntax for the loop has changed.

Funkys letoscripts do it this way:

for (%mod ['*.git]) {

But with the new version it must be:

for ('*.git' in %mod) {

Seems to me, that the previous version got tons of changes, I can't outguess... Need some more digging

[Proleric]

I verified that behaviour. Existing scripts fail with this message:

[Warning] Deprecated use of %ERF['resource']; use instead 'resource' in %ERF at c_add_var.ls line 9 pos 6.

So, I'm even more persuaded to stay on the old release. All the same, it would be really helpful if you could publish the documentation in a legible format, with the caveat that some things have changed. It's full of helpful gems!

As one illustration, in Funky's example #1, there's no way of telling which area each placeable count is for, because the area name isn't in any .git file field. However, using the new documentation to discover the "silver bullet" variable $_,

for (%mod['*.git']) 
  {
    $area = $_;
    $count = 0;
    for (/{'Placeable List'}) {$count++;}
    print $area, $count, "\\n";
}

[MrZork]

It is also possible to give the loop variable an explicit name. The example below does that in both loops.

 

FWIW, the example is a placeable counter, as above, but also prints the more human-readable name of each area, along with its resref and placeable count. To do that, the first loop populates a hash with the area names, using the resrefs as keys, then the second loop grabs the name. Both loops take advantage of the fact that the resrefs are the ARE and GIT filenames stripped of their extensions, something ls scripts can also take advantage of when looping through creatures, items, etc.

@AreaNames = ();
for $AreaARE (%mod['*.are']) {
    $AreaNames[substr($AreaARE,0,-4)] = /Name;
    }

for $AreaGIT (%mod['*.git']) 
    {
    $AreaRR = substr($AreaGIT,0,-4);
    $AreaName = $AreaNames[$AreaRR];
    $count = 0;
    for (/{'Placeable List'}) {$count++;}
    print "$AreaName [$AreaRR] has $count placeables\n";
    }

[dunahan_schwerterkueste_de]

Sry, for that delay Got the doc ready enough for the first public release. Hope it will help, even a littlebit

 

Here's the link

https://www.dropbox....your Module.pdf

 

The code for the first example of Funky will work, if you do it that way:

Spoiler

%mod = 'YOUR_MOD_NAME_HERE.mod';
for ('*.git' in %mod) {
  $count = 0;
  for (/{'Placeable List'}) {
    $count++;
  }
  print $count, ";\n";
}

for (*.are' in %mod) {
  $tiles = 0;
  for (/{'Tile_List'}) {
    $tiles++;
    }
  print /Tag, " ; ", /Name, " ; ", /ResRef, " ; ", $tiles, " ;\n";
}

MrZork explains the definition of subroutines, as I guess. It's described in the helpsys also in the pdf-doc.

[dunahan_schwerterkueste_de]

As you can see in this very early version, I'm trying to build a lexicon like the nwscript-lex got some of the functions of rc3 and some of Funky's/Acaos provided scripts working in the new version of moneo.

*working on these files to get them right*

[FunkySwerve]

Very cool, and nice work. Watching this thread with interest, though I don't have time to do much experimentation myself, these days. Let me know if there's anything you think should be included in the original posts.

 

Thanks!

Funky

[dunahan_schwerterkueste_de]

*blushes*
Thanks you too! Got 70% of those provided scripts by you and Acaos already working. Now I'm trying to get the doc filled with the info I got of this 'learning by doing' sessions
Besides, I'm going to comment those scripts, so that even newbies, like me (got no education on languages to write such scripts, learned only from tests and faults) can read them and have a idea of what they do, or even what help moneo can be!
*going back to this script, that eventually copies a whole area from one map to another map, or I hope so*

[dunahan_schwerterkueste_de]

Something I found out and would add to the doc in time:

Spoiler

/*
Use of add($WhereToAdd, $ValueToAdd, $TypeToAdd)
Adds to $WhereToAdd the Value $ValueToAdd with the Type $TypeToAdd.
$ValueToAdd and $TypeToAdd are undefined, so they can be listed in
the function in a random order.
But it had been proofed that the following order is best readable:
add $WhereToAdd, $TypeToAdd, $ValueToAdd

Has the subflags /copyfrom, $lang, $setifexists, which I hadn't
used till jet.
*/

Spoiler

/*
Use of substr(SearchableString, StartingAt, AmountLetters) eq 'StringToSearch';
Searches from left to right for StringToSearch in SearchableString. Beginning at
StartingAt and counts AmountLetters from that point. StartingAt can be negative,
if you want to start from the right counting to the left.
*/

Spoiler

/*
Use of arrays. Declare an array like this:
@NameOfArray = ('$array01', '$array02', '$array03', '...');
@NameOfArray consists of values '$array01', '$array02', '$array03' and
many more...
Note that keys do not require quotation (unless they contain spaces or other
reserved characters), and values can be of any type (the same is true of
arrays). Accessing and assigning to hash elements uses standard list syntax.
*/

Spoiler

/*
Special use of print(StringToPrint);
Note that some strings can't be printed easily if they are childrens of
a list (/~/****). Especially AreaProperties, Door List and Placeable List
in a git-file. Those must be listed separately.
*/

[FunkySwerve]

Sounds good. Do you have a script sample for those functions?

 

Thanks,

Funky

[dunahan_schwerterkueste_de]

Got them here, but had to correct some descriptions due newer experiences...

 

addac.ls

Spoiler

// addac.ls
// Script provided by FunkySwerve, HigherGround
// Changed to syntax version 4.0.6.27rc3, dunahan@schwerterkueste.de
// Added logging for debug

// Adds a integer variable named "ItemProperties_Mask" with a value of 16
// to a specified creature-file.
// Prints the result at the end of the script to a logfile.

/*
Use of add($WhereToAdd, $ValueToAdd, $TypeToAdd)
Adds to $WhereToAdd the Value $ValueToAdd with the Type $TypeToAdd.
$ValueToAdd and $TypeToAdd are undefined, so they can be listed in
the function in a random order.
But it had been proofed that the following order is best readable:
add $WhereToAdd, $TypeToAdd, $ValueToAdd

Has the subflags /copyfrom, $lang, $setifexists, which I hadn't
used till jet.
*/

%utc = 'PLACE_YOUR_FILE_HERE.utc' or die$!;
$debug = 'yes';

add /VarTable, type => gffList unless /VarTable;
add /VarTable/Name, type => gffString, value => "ItemProperties_Mask";
add /VarTable/[_]/Type, type => gffDword, value => 1;
add /VarTable/[_]/Value, type => gffInt, value => 16;

if ($debug eq 'yes') {
print "Name;ResRef;\n";
print /FirstName, ";", /TemplateResRef, ";\n";
print "Variable;Value;\n";

for (/VarTable) {
if (/~/Name eq 'ItemProperties_Mask') {
     print /~/Name, ";";
     print /~/Value, ";\n";
}
}
}

%utc = '>';
close %utc;
// dumbposs.ls
// Script provided by dunahan@schwerterkueste.de
// Syntax version 4.0.6.27rc3

// Prints all monsters in module if their resref ends with boss.

/*
Use of substr(SearchableString, StartingAt, AmountLetters) eq 'StringToSearch';
Searches from left to right for StringToSearch in SearchableString. Beginning at StartingAt and counts AmountLetters from that point. StartingAt can be negative, if you want to start from the right counting to the left.
*/

%mod = 'PLACE_YOUR_FILE_HERE.mod' or die$!;
$startat = -4;
$countletters = 4;
$searchfor = 'boss';

print "Name;ResRef;SpawnScript;CR;CR-Adjust;\n";

for ('*.utc' in %mod) {
if (substr(/TemplateResRef, $startat, $countletters) eq $searchfor) {
print /FirstName, ";", /TemplateResRef, ";", /ScriptSpawn, ";", /ChallengeRating, ";", /CRAdjust, ";\n";
}
}

close %mod;

 

dumpcritter.ls:

Spoiler

// dumpcritter.ls
// Script provided by FunkySwerve, HigherGround
// Changed to syntax version 4.0.6.27rc3, dunahan@schwerterkueste.de
// Added some titles to the table, so its easier to read.

// Prints for the defined creature-file all info's of it.

/*
Use of arrays. Declare an array like this:
@NameOfArray = ('$array01', '$array02', '$array03', '...');
@NameOfArray consist of the values '$array01', '$array02', '$array03' and
many more.
Note that keys do not require quotation (unless they contain spaces or other
reserved characters), and values can be of any type (the same is true of
arrays). Accessing and assigning to hash elements uses standard list syntax:
*/

%utc = 'PLACE_YOUR_FILE_HERE.utc' or die$!;

@classes = ( "Bbn", "Brd", "Clr", "Drd", "Ftr", "Mnk", "Pal", "Rgr", "Rog", "Sor", "Wiz", "Abr", "Anm", "Cns", "Hum", "MoH", "Ele", "Fey", "Drg", "Und", "Com", "Bst", "Gnt", "MaB", "Out", "Shp", "Ver", "Shd", "Har", "ArA", "Asn", "Blk", "CoT", "WpM", "PMa", "Shf", "DwD", "RDD", "Ooz", );

print "ResRef;FirstName;CR;";
print "ClassLvl;Str;Dex;Con;Int;Wis;Cha;fortbonus;refbonus;willbonus;NaturalAC;EnergyImmunities;";
print "EnergyResistance;OtherImmunes;SpellImmunes;Soak;NoPet;SR;DodgeAC;DeflectionAC;NaturalAC;\n";

print /TemplateResRef, ";", /FirstName, ";", /ChallengeRating, ";";

$val = "";

for (/ClassList) {
$val = $val + "|" if $val ne "";
$cls = /~/Class;
$val = $val + $classes[$cls] + /~/ClassLevel;
}

print $val, ";", /Str, ";", /Dex, ";", /Con, ";", /Int, ";", /Wis, ";", /Cha, ";", /fortbonus, ";", /refbonus, ";", /willbonus, ";", /NaturalAC, ";";

$val = "";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'EnergyImmunities';
}

print $val, ";";

$val = "";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'EnergyResistance';
}

print $val, ";";

$val = "";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'OtherImmunes';
}

print $val, ";";

$val = "";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'SpellImmunes';
}

print $val, ";";

$val = "0+0";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'Soak';
}

print $val, ";";

$val = "";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'NoPet';
}

print $val, ";";

$val = "";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'SR';
}

print $val, ";";

$val = "0";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'DodgeAC';
}

print $val, ";";

$val = "0";
for (/VarTable) {
$val = /~/Value if /~/Name eq 'DeflectionAC';
}

print $val, ";";

$val = "0";

for (/VarTable) {
$val = /~/Value if /~/Name eq 'NaturalAC';
}

print $val, ";";
print "\n";

close %utc;

 

dumpdoors.ls:

Spoiler

// dumpdoors.ls
// Script provided by dunahan@schwerterkueste.de
// Syntax version 4.0.6.27rc3

// Prints all doors of all areas with a pre-defined OnOpen-Script.
// Added a option to replace the OnEnter script and save file.

/*
Special use of print(StringToPrint);
Note that some strings seem not to be printed easily if they are childrens
of a list (/~/****). Especially AreaProperties, Door List and Placeable
List in a git-file. Those should be listed separately.
*/

%mod = 'PLACE_YOUR_FILE_HERE.mod' or die$!;
$script = 'PLACE_YOUR_SCRIPT_HERE';
$rplace = ''; // Leave empty if you don't want to change the scripts

print "Nbr;Door;Tag;Link;OnOpen;NewOnOpen;\n";

for ('*.git' in %mod) {
$nbr;
$count = 0;

for (/{'Door List'}) {
if (/~/OnOpen eq $script) {
     $nbr++;
     $count++;

     if ($count > 0) {
     print $nbr, ";";
     print $count, ";";
     print /~/Tag;
     print ";";
     print /~/LinkedTo;
     print ";";
     print /~/OnOpen;
     print ";";
     }

     if ($rplace ne '') {
     /~/OnOpen = $rplace;
     print /~/OnOpen;
     print ";";
     }

     print "\n";
}
}
}

if ($rplace ne '') {
%mod = '>';
}

close %mod;

 

*grumbles 'cause of the formatting of the post due inserting from mobile phone*

[FunkySwerve]

Actually, I get the same formatting issues when I post from my PC. I haven't fussed with trying to work around them yet, as I've been using pastebin. I may do that as well, for these samples. I'll get them added to the followup post as soon as I'm able.

 

Thanks!

Geoff

[Proleric]

On the subject of formatting on this site, you can use the "spoiler" BBCode to reduce long scripts to a button - that way, folk can browse the thread without having to page through the detail every time.

[dunahan_schwerterkueste_de]

Didn't saw this spoiler thingie, so I didn't thought it was active. Now I re-edited the post and put them into spoilers

[dunahan_schwerterkueste_de]

Sry, got some serios probs with akamaihd.net Since I did some backups, my work isn't destroyed, but it would take some time to get back to it...

[FunkySwerve]

Thanks - I'll try to reformat the original post, when I go back through it, using spoiler tags. Here's to hoping this forum holds on to color codes better than the last one.

 

Funky

[Proleric]

I just discovered how to merge area information from the .are and .git files. I'll cross-post the solution here, for future reference. In this example, we make a list of area placeables from the .git file, but add the area name from the .are file.

 

Spoiler

# Find all placeables with a given script by area
%mod = 'c:\NeverwinterNights\nwn\modules\Dark Energy.mod' or die;
for (%mod['*.git'])
  {
    $area = substr($_, 0, -4);
    %are = %mod[$area + '.are'];
    $areaname = /Name;
    close (%are);    
    for (/{'Placeable List'})
      {
        if (/~/OnHeartbeat ne '')
          {print $area, ";", $areaname, ";", /~/TemplateResRef, ";", /~/OnHeartbeat,";", "\n";}
      } 
  }