if we get is faster load times, less lag, and an expanded pallet, i'd be so happy that i'd be in pain. now if we ONLY get those things, and thats absolutely the ONLY thing that we get, I'd be pissed, after all, thats all data would be doing. data isn't the only one who does anything to the game now. however, what does that have to do with an external editor?

And actually yes, there was an external editor, in the B19-21 timeframe, I was helping the guy beta test it. I still have it somewhere, although it is not compatable with this build, and it was horribly disorganized. the only thing that came out of it that worked was a RTE tester, that would load all the base files, then a specific mod to check for errors, and references to outside rte's. make sure it isn't out of order or missing something. It would return all errors, not just the first one encountered, and it would tell you if files where missing. and also, no, that doens't work this build either, because some stuff got re-named.

Actually I think i might be wrong about time-frame, it broke when data added the dreadnought... i can't remember which build that was, but you can tell it was a long time ago.



Weasel's little post hints that A) next build is soon, as well as either B) changes to how things work, IE anything you make would need re-made, or C) bundled editor.

a new editor, or massive changes, would make anything you make useless. now if you only get as far as the interface, and data doesn't add an editor, then your good, at least cause it will be a while till the next build.

Or else he's just saying that the new build may break what OP is building, so if he wants to save himself some effort he should wait.

As long as you put emphasis on "may" that's the most accurate, yes

Wow, quite the response. It's settled then. I'll get started on this and try to get a prototype rolling ASAP. I highly doubt Data would change the structures so terribly bad that it derails every single little thing , though it might take adaptability - Good code, people, is what it's about I'll start on the offsets editor.

One huge thing that worries me is I always feel like i'm missing some other facet. I know of the CC wiki that explains how some things work, but a lot of the fiddly little parameters aren't very well define - Anyone willing to throw me a bone on this? I've only learned by colliding other mods together at high speeds then loving whatever bastard child pops out. I'm going to slowly go into making a fully functional devices/actors editor as well and extend onwards, I just need a little guidance on everything allowed, Objects and their types/modes.

If anyone wishes to help:

AIM: CookMyMongoose
MSN: noxthox@hotmail.com

A walkpath editor would be so neat-o.

I would highly advise breaking up your email address so that bots can't read it.
Otherwise you may soon be afloat upon the great sea o' spam.
Just say'n.

Good advice, but i'm not worried. It's a black hole email box anyways.

....Not cool man, not cool.


Very very few of us understand those.

There is an actor editor and Roon3's limbpath tutorial for the learning with.

I learned how in a day. It makes complete sense after you figure it out, kinda like offsets.

that was kind-of my point. you just need to sit down with these things and nut them out. well, for quite a lot of them you dont (for example, defining a presetname should take <3 seconds to understand and be able to implement, but understanding the concept of recursive gibbing might take a bit longer, as would figuring out how to mirror another actor's actions with controller functions, horizontally flipped.
but hey, if editors come and simplify it for everyone who doesnt currently get it, more power to them.

I'm not saying it's impossible. All the offsets are easy for the exception of walkpaths. Those can take hours.

Of course it isn't impossible. And, after you learn them, they are as easy as regular offsets, which was my point. The only problem I've had is figuring out how far the leg will actually extend, which is just a bit of playing with it.

They still take a long time.

This is getting petty. It depends on how complex the limbpath is, but overall if a walkpath takes you longer than 15 minutes to get right, take a break, do something else, then come back to it. All they are is instructions in segments of "move the hand/foot x pixels across and y pixels up and down", which if you draw up a diagram of how you want it to work doesnt take very long to get right.