Author Topic: I think it's time to work on the Techs  (Read 16631 times)

Mauron

  • Guru of Reason Emeritus
  • Errare Explorer (+1500)
  • *
  • Posts: 1768
  • Nu-chan
    • View Profile
    • Maurtopia
Re: I think it's time to work on the Techs
« Reply #120 on: February 24, 2008, 06:46:00 am »
I removed the C0 at the start of Cyclone once, and it didn't end properly.

Tomorrow I'll look into this more.

Agent 12

  • Zurvan Surfer (+2500)
  • *
  • Posts: 2572
    • View Profile
Re: I think it's time to work on the Techs
« Reply #121 on: February 28, 2008, 01:52:26 am »
I'm pretty sure 24 XX is wait here until time XX.  And the current XX is controlled by the code before 2E 01 00. 

1B XX
73 00
72 XX seems to be a  new object. 

Example

Code
Code
Code
24 02  <----  All code waiting for 02 begin
code
code 03 <--- All code waiting for 03 begin
2E
01
00

1B 03
73 00
72 03  <-----New object
24 02  <-----Don't move until the above 2402 is started
code
code
  00

1B 03
73 00
72 03
code
code
24 03 <-----Don't move until the above 24 03 is started



That is my current theory for code organizaiton, i think the next version of the editor might make subtrees within object.....and maybe use coloring to show divisions of time.


--JP









Agent 12

  • Zurvan Surfer (+2500)
  • *
  • Posts: 2572
    • View Profile
Re: I think it's time to work on the Techs
« Reply #122 on: April 28, 2008, 08:57:06 pm »
I believe the way the next section of code starts is with 36....it's like section plus plus

Beginning of code $section = 0

Most techs seems to have a set up period and then a 36.   Sorry I forgot to make the header editable for this release.

That damn C0 still keeps popping up everywhere I look.  Also  D9 30 (30 is a parameter but i only see D9 with 30)  and....let me look it up........0D XX

--JP

Agent 12

  • Zurvan Surfer (+2500)
  • *
  • Posts: 2572
    • View Profile
Re: I think it's time to work on the Techs
« Reply #123 on: April 29, 2008, 03:31:53 pm »
OK, much like  24 XX is a lock until there is an EndSecition command (36)  23 XX is a lock until another command....unfortunately this one is not as pretty as the other.

It seems at this point that the way to increment 23 XX's lock is by the following commands:

78 XX XX
Animation

.....yea i know it's ugly but those from what I can tell those commands must be together 78 is a variant of a call sound command.

So basically there are two different "Locks" for controlling flow of a tech....here is an example

Code: [Select]
HEADER:            <-----$section = 0     $subsection = 0
//Caster Object
<start up code>
END Section        <------$section = 1
<section 1 code>
24 02                 <------wait here for $section to = 2
<section 2 code sub section 1>
23 01               <------wait here for $subSection = 1
<section 2 code sub section 2>
2E 01 00          <------End Tech


//Object like a fireball
<start up code>
24 01                <-----$wait here for $section to = 1
<section 1 sub section 1 code >
78 XX XX           
Animation           <-------$subSection = 1
Return
<section 1 sub section 2 code>
END Section        <------$section = 2


Hopefully there is something i'm missing to make a more elegant solution.  I dont know why they used 2 different locks since they just as easily could have had 24 XX with many many sections.  I really hope those two commands don't have to go together but when I remove either one of them the tech crashes.....

--JP



« Last Edit: April 29, 2008, 03:33:27 pm by jsondag2 »