About LINE opcode.

  • Thread starter Thread starter Akari
  • Start date Start date
Status
Not open for further replies.
Akari: added SLINE which may be of interest since you have implemented LINE, I think. Of note is that whilst you can define multiple LINEs in one entity as mentioned previously, SLINE only allows you to update the first defined LINE; multiple calls to SLINE will still only update the first one.
 
Akari: added SLINE which may be of interest since you have implemented LINE, I think. Of note is that whilst you can define multiple LINEs in one entity as mentioned previously, SLINE only allows you to update the first defined LINE; multiple calls to SLINE will still only update the first one.
Click to expand...
Ok. I'll add this to my todo. But... hmm I didn't know that we could define a lot of lines in one entity. Is this used somewhere?
 
No, it's not used in the game as far as I know, but you did ask up there ^....

Next: What will happened if I define two or three lines in entity?
Click to expand...
Yes, one entity can define multiple LINEs and they will each exist & execute the relevant script, so there's no cancelling out of previous definitions.
Click to expand...
Don't worry about it, I'd say it's an undefined behaviour.
 
No, it's not used in the game as far as I know, but you did ask up there ^....

Next: What will happened if I define two or three lines in entity?
Click to expand...
Yes, one entity can define multiple LINEs and they will each exist & execute the relevant script, so there's no cancelling out of previous definitions.
Click to expand...
Don't worry about it, I'd say it's an undefined behaviour.
Click to expand...
Ups sorry. I didn't notice that (or forgot it). ^^''
 
Script 2: Activates once when a button is pressed.
Script 3: Activates once when you move into the object/line. When you stop, and then move again, the script activates (provided you're still in the object/line, of course).
Script 4: Not sure. Seems similar to 3
Script 5: Activates repeatedly whilst you are on the object/line.
Script 6: Activates once when you move into the object/line; will not reactivate until you leave and re-enter.
Script 7: Activates once only when you have left the object/line.
Click to expand...
I have few more question about it.

1) As I can see script 3 activates on collide with solid range or line and script 4 activates when point cross line (point that defined entity position). Synergy Blades can you confirm it?

2) I cant activate script 4-7 to field object although they all works with LINE. Maybe they are not working with field object at all? Script 3 always RET in field objects although Script 4 may be defined. Does this true? Can you check it?

3) Script auto activation don't work if entity not solid?
 
Last edited:
1) Yes... I think that's right. Of course for Script 4 you can't really test this with a field object, because to produce it the entity must be solid (see point 3), but if you try it with a LINE such as a save point, script 4 only works right in the very center of the line, whilst script 3 (and indeed 5 to 7) activates right along the line. So I think this is a reasonable assumption.

2) 4 to 7 don't seem to work with field objects, as you suggest, solid or not. This isn't like point 1, where it only works in the center of the object/line, because if you try these scripts on the LINE they work anywhere along it, unlike with Script 4 where you have to be right in the center. So yes, LINE only.

3) If it's not solid (i.e SOLID(1)) none of these special scripts activate. That's why save points have an extra entity using a LINE to do the dialog and sound they produce.
 
1) Yes... I think that's right. Of course for Script 4 you can't really test this with a field object, because to produce it the entity must be solid (see point 3), but if you try it with a LINE such as a save point, script 4 only works right in the very center of the line, whilst script 3 (and indeed 5 to 7) activates right along the line. So I think this is a reasonable assumption.

2) 4 to 7 don't seem to work with field objects, as you suggest, solid or not. This isn't like point 1, where it only works in the center of the object/line, because if you try these scripts on the LINE they work anywhere along it, unlike with Script 4 where you have to be right in the center. So yes, LINE only.

3) If it's not solid (i.e SOLID(1)) none of these special scripts activate. That's why save points have an extra entity using a LINE to do the dialog and sound they produce.
Click to expand...
mmm I still don't see whole picture =(

In case of line: whats the difference between 3 and 6? They both works OnEnter... whats the difference?

What do you mean by the very center of the line? (Line 1---------2---------3) It only activate when you reach point 2 and not activated when you reach 1 or 3? And does this includes solid range of PC entity or not?

And I have one more question, does line have talk range and can it be talked to?

Please write the all auto script activation for line and field object.
 
I think he means when the center of the characters body crosses the line. That would be my guess.

Cyb
 
I ought to start by saying that I think a line has a designated talk and solid range (that cannot be changed with SLIDR/TALKR, I tried). It's only a small amount, but it's enough that it makes sense to be able to "enter" and "leave" a line (or more precisely, its range) and talk to it from a specific distance.

What do you mean by the very center of the line? (Line 1---------2---------3) It only activate when you reach point 2 and not activated when you reach 1 or 3? And does this includes solid range of PC entity or not? And does this includes solid range of PC entity or not?
Click to expand...
Seems I wasn't quite right on script 4. It's the center point of the character object that has to enter the line, i.e this disregards the Solid Range of the object entering the line.

whats the difference between 3 and 6?
Click to expand...
3 activates once when you move within the line range; when you stop, then move again, it activates again. With 6, it activates once when you are within the line range, but you have to leave the line area and then re-enter it for it to activate again. This stops it from repeatedly activating whilst you move along the line.

And I have one more question, does line have talk range and can it be talked to?
Click to expand...
You can talk to a line, but it does not have a talk range (TLKR has no effect). So I suppose talk range is tied to the field object whilst lines have a predetermined talk range, which is probably the same as its "solid range" used for entering/leaving the line.

So in the end I think it boils down to this:

Line


  • 1: Init
  • 2: OnTalk - the talk button has been pressed with the character on the line's range; script activated once.
  • 3: OnMove - the character has moved whilst on the line; script activated once. Move again on the line, and the script activates again.
  • 4: OnCenter - the center point of the player object has moved on the line; script activated once. Move again on the line, and the script activates again. Disregards solid range.
  • 5: OnInside - the character is on the line range; script activated repeatedly, once every frame.
  • 6: OnEnter - the character has entered the line area; script activated once. Move again on the line, nothing happens. Must exit and re-enter line range for effect to occur again.
  • 7: OnLeave - the character has left the line area; script activated once. Move again on the line, nothing happens. Must exit, re-enter, and re-exit the line range for effect to occur again.

Object


  • 1: Init
  • 2: OnTalk - the talk button has been pressed; script activated once.
  • 3: OnMove - the character has moved onto/touched the edge of the solid range; script activated once. Move again whilst still on the edge of the solid range, and script activates again.

OnCenter cannot be used because the center of the player character object cannot reach the solid object; OnInside, OnEnter and OnLeave also do not work with objects, only with lines.


If I seem vague or it seems like I'm not answering your question, my apologies, it's mostly because I am unsure myself.  :-D Not always easy to explicitly say what it appears to be doing by observation.
 
Last edited:
Hello again Synergy Blades =)

Can you try to guess at which priority scripts run. Cause they seems not run at priority 0. There are a lot of conflict when i try to run some script and this priority already taken.

Please try to run cycled script in some slot and watch if script activation runs or not. We only know that slot 7 are reserved for initialisation base script.
 
I assume you mean LINE scripts, when executed by a field object crossing? I put a cycled request in the director script, that executed the script from the line entity which when crossed, plays a sound and waits for about a second. So I can hear once a second or so the save point sound. If you cross the line, the sound plays instantly, no matter what stage of execution the cycled sound is at. So would it be right to say the line script runs at top priority, like the initialisation?
 
I assume you mean LINE scripts, when executed by a field object crossing? I put a cycled request in the director script, that executed the script from the line entity which when crossed, plays a sound and waits for about a second. So I can hear once a second or so the save point sound. If you cross the line, the sound plays instantly, no matter what stage of execution the cycled sound is at. So would it be right to say the line script runs at top priority, like the initialisation?
Click to expand...
Mmm.... I dont understand what you did =)

Two tests:

Create entity with line.
Start cycled script at slot 2 (OnEnter) with priority 0
Then enter this entity.
Result?

Create entity with line.
Start script at slot 2 (OnEnter) with priority 0 and make it wait for something. (Message for example)
Then enter this entity.
Result?
 
I finalize the info about script activation. I finish reversing this part of code.
Everything Synergy Blades talk was true.

Line

    * 1: Init
    * 2: OnTalk - the talk button has been pressed with the character on the line's range; script activated once.
    * 3: OnMove - the character has moved whilst on the line; script activated once. Move again on the line, and the script activates again.
    * 4: OnCenter - the center point of the player object has moved on the line; script activated once. Move again on the line, and the script activates again. Disregards solid range.
    * 5: OnInside - the character is on the line range; script activated repeatedly, once every frame.
    * 6: OnEnter - the character has entered the line area; script activated once. Move again on the line, nothing happens. Must exit and re-enter line range for effect to occur again.
    * 7: OnLeave - the character has left the line area; script activated once. Move again on the line, nothing happens. Must exit, re-enter, and re-exit the line range for effect to occur again.


Object

    * 1: Init
    * 2: OnTalk - the talk button has been pressed; script activated once.
    * 3: OnMove - the character has moved onto/touched the edge of the solid range; script activated once. Move again whilst still on the edge of the solid range, and script activates again.
Click to expand...
Little addition:
Visible entitys OnTalk only work with first entity that wish to activate script. All others will be skipped.
Lines activate all OnTalk request.
Lines OnTalk activates during move. If your coordinates not changed - OnTalk will not be activated.

All sctipts starts at priority 1. Like all other requests if entity already execute script with higher or same priority - request will be skipped.

I think this is topic is finished =)
 
First of all I am glad people are still working in spite of loosing our fearless leader <TM>
:D

As I am uncertain where to start I started by getting OGRE demo's compiling on my machine.

Erstwhile (back to what you were speaking of).  Interesting it looks like it fires an event and the first object catches it.
This is kind of like Kingdom Of Kroz coding (early 90's game on the PC) with objects. I am now suspicious of how the script code was generated.

My guess is it's not entirely written script code i suspect they may have made some tools for making things work.
In general I throw debug code into my stuff to spew out things when needed/wanted or desirable.
Have either Akari or G found said code? From my perusal of FF7's it appears there is some in there (printf format specifier strings appear in the program). These go out to the console correct?  Hmmm

Cyb
 
Status
Not open for further replies.
Back
Top