From The Mana World
(EOF newline & NPC section suggestion)
 
(8 intermediate revisions by 3 users not shown)
Line 3: Line 3:
Perhaps we should regulate comments?
Perhaps we should regulate comments?


==EOF newline==
===Proposal===
I’m working on a proposal [[User:Kess/eAthena scripting|here]]. Earlier comments on what was here follows below. ✎ [[User:Kess|Kess]]<sup>[[User talk:Kess|☽]]</sup> 04:11, 19 October 2008 (CEST)
 
====On ending script files with a newline====
I’d like to propose that all script files should have a mandatory newline at the end of file, to ease working with shell scripts on these files. —[[User:Kess|kess]] 14:01, 14 October 2008 (CEST)
I’d like to propose that all script files should have a mandatory newline at the end of file, to ease working with shell scripts on these files. —[[User:Kess|kess]] 14:01, 14 October 2008 (CEST)


==NPC section suggestion==
====On NPC section suggestion====
The NPC section isn’t there yet, and while I do not know it. Here’s a beginning text someone might be able to work off from. Note that the NPC script in '''new_37-1-woodland-mine/miners.txt''' has two additional values just before the start of the script section.
Yeah, I never got around to doing this. The first question mark is the direction (I assume facing direction, 8 compass values available), which we don't use. The second two are indeed optional. They define an activation area, which only that one NPC uses (to warn you when you get too close). The only thing we need to do is determine how the numbers for the activation area work. &mdash; [[User:Jaxad0127|<span style="color: #160196">Jaxad</span>]][[User Talk:Jaxad0127|<span style="color: #5B038F">0127</span>]] 17:51, 14 October 2008 (CEST)
 
NPCs are defined like this:
 
''map'',''x'',''y'',''?''<TAB>script<TAB>''name''<TAB>''spriteID'',['''?''','''?''',]{
:''script''
}
 
Where


* '''map''' is the map the NPC is located in
The name is used, it shows below the npc. [[User:EJlol|EJ]] 10:42, 15 October 2008 (CEST)
* '''x''' is the x-coordinate of the NPC
* '''y''' is the y-coordinate of the NPC
* '''?''' is ...
* '''name''' is the name of the NPC, '''''is this also unused?'''''
* '''spriteID''' is the NPC sprite identifier
* '''?''' is ...
* '''?''' is ...
* '''script''' is the scripting code, see below


—[[User:Kess|kess]] 14:01, 14 October 2008 (CEST)
: Is it possible to use ''name'' as a constant in the script part? Something like:
mes "["+@NAME$+"]";
mes "\"Dialogue...\"";
: ✎ [[User:Kess|Kess]]<sup>[[User talk:Kess|☽]]</sup> 13:48, 15 October 2008 (CEST)

Latest revision as of 03:48, 20 April 2020

Irving Rivas, 31/7/07:

Perhaps we should regulate comments?

Proposal

I’m working on a proposal here. Earlier comments on what was here follows below. ✎ Kess☽ 04:11, 19 October 2008 (CEST)

On ending script files with a newline

I’d like to propose that all script files should have a mandatory newline at the end of file, to ease working with shell scripts on these files. —kess 14:01, 14 October 2008 (CEST)

On NPC section suggestion

Yeah, I never got around to doing this. The first question mark is the direction (I assume facing direction, 8 compass values available), which we don't use. The second two are indeed optional. They define an activation area, which only that one NPC uses (to warn you when you get too close). The only thing we need to do is determine how the numbers for the activation area work. — Jaxad0127 17:51, 14 October 2008 (CEST)

The name is used, it shows below the npc. EJ 10:42, 15 October 2008 (CEST)

Is it possible to use name as a constant in the script part? Something like:
mes "["+@NAME$+"]";
mes "\"Dialogue...\"";
✎ Kess☽ 13:48, 15 October 2008 (CEST)