K-Editor v1.12

[Phoenix-D]

I'll check the new Version out and let you know what I think. If it does tech-grid components well, it'll be a real time-saver. Those are extremely tedious to do by hand..

Phoenix-D

[DavidG]

Originally posted by Phoenix-D:
I'll check the new Version out and let you know what I think. If it does tech-grid components well, it'll be a real time-saver. Those are extremely tedious to do by hand..

Phoenix-D

Can you explain what you mean by a "tech-grid component"?

[ January 03, 2003, 23:53: Message edited by: DavidG ]

[Krsqk]

Sometimes called a dimensional component. Take each tech requirement, and it's one dimension to the matrix. Two requirements generates a "square" component, three requirements generates a "cube" component, etc. This would be useful, for example, to create missiles with separate tech levels which affect range, damage, and speed. Here's a sample 2-dimensional component with "sides" of "size" 3; the numbers represent tech levels.

code:

---

Damage:  1     2     3

Range:

  1     1/1 | 1/2 | 1/3

  2     2/1 | 2/2 | 2/3

  3     3/1 | 3/2 | 3/3

---

Notice that instead of 3 component levels, there are nine. With a three dimensional component, there would be 27:

code:

---

Speed:         1           ||           2           ||           3

     1/1/1 | 1/1/2 | 1/1/3 || 2/1/1 | 2/1/2 | 2/1/3 || 3/1/1 | 3/1/2 | 3/1/3

     1/2/1 | 1/2/2 | 1/2/3 || 2/2/1 | 2/2/2 | 2/2/3 || 3/2/1 | 3/2/2 | 3/2/3

     1/3/1 | 1/3/2 | 1/3/3 || 2/3/1 | 2/3/2 | 2/3/3 || 3/3/1 | 3/3/2 | 3/3/3

                           ||                       ||

---

As you can probably imagine, this gets very cumbersome to hand-code, as well as being very error-prone. These issues grow exponentially with every additional dimension or "size" increase.

[ January 04, 2003, 04:42: Message edited by: Krsqk ]

[Krsqk]

Bump...was that a clear explanation?

[Phoenix-D]

Hmm. Having a bit of a problem making a tech-grid component.

Everything is working decently, if not quite how I expected..but the "range at base damage" entry isn't. No matter what I do with that field, the range of the component never changes.

Phoenix-D

[DavidG]

Originally posted by Krsqk:
Bump...was that a clear explanation?

Still a bit fuzzy (at least with the 3d one) but I think I get the general idea. Thanks.

< Ediot > OK tried your program again after actually reading the readme file so I get it now. Pretty cool!

[ January 12, 2003, 01:05: Message edited by: DavidG ]

[DavidG]

Originally posted by Phoenix-D:
Hmm. Having a bit of a problem making a tech-grid component.

Everything is working decently, if not quite how I expected..but the "range at base damage" entry isn't. No matter what I do with that field, the range of the component never changes.

Phoenix-D

This is what I found too.