Program to make the creation of mods easier.

posted on July 23rd, 2011, 1:16 pm

a nice project idea! me likes visual studio (all of my FO tooling is done in .net by the way, VB for the most part with a bit F#)

for the past patches i'm working on a complete redo of my internal toolchain, with the option to make at least parts of it releasable. yet, as it grew over about 12 years, thats quite a voyage. And as everybody knows who worked with "grown" but "designed" software: its a terrible one

posted on July 23rd, 2011, 2:17 pm

I think Starbase34 has a corrected list of A2 commands, IIRC it's quite extensive.

Unfortunately it also is not complete and copies many of the same mistakes as BBoM and adds a few of its own. 

posted on July 28th, 2011, 6:05 pm

a nice project idea! me likes visual studio (all of my FO tooling is done in .net by the way, VB for the most part with a bit F#)

*pfft* F#. Sorry, but isn't F# kind of a joke, and didn't it got canned back with VS 2005, or am I wrong?

for the past patches i'm working on a complete redo of my internal toolchain, with the option to make at least parts of it releasable. yet, as it grew over about 12 years, thats quite a voyage. And as everybody knows who worked with "grown" but "designed" software: its a terrible one

I know the feeling. It starts with lets put this into a function and that into a function and this other thing can be made its own class. Then fifty functions and five classes later you have no idea what's going on any more.

Also Optec, I don't know if you're the one in charge of FPQEdit, but is there any chance of exposing the packing and unpacking functions as a library or something?

Glad to hear of your successes Atlantisbase

We will be completing the list of nested ODF commands and classlabels eventually, but it requires a lot of work from Doca and thus will still take some time. However, it will be done eventually . At the very least, so far, a complete weapons' ODF tool could probably be created  . I would be careful relying on the BBoM for the ODF commands, as there are quite a few errors present - either commands that do not exist/do not function, or are wrong in their description/usage 

So then I take it there is currently no definitive list. What I really need to know is what commands are valid for what kinds of objects and what type they take.

On that note, perhaps someone can clarify something. I know there are some commands that take file names. So my question is, can any command that takes a string potentially take a filename, or can only certain commands take a file name?

I would like to hear thoughts on what the interface for the main ODF editing system should be, since you people are the ones who will use it.

posted on July 29th, 2011, 1:17 pm

I'd send Doca a PM about the FPQEdit stuff

Yes, only certain commands can take filenames.

Right now I have a hierarchy of all classlabels that is finished for each super class, but only a partial hierarchy for the commands - the Weapon hierarchy is totally complete, and a list of base commands for GameObjects is also complete.

posted on July 29th, 2011, 2:02 pm

*pfft* F#. Sorry, but isn't F# kind of a joke, and didn't it got canned back with VS 2005, or am I wrong?

I believe you're thinking of J#.

posted on July 29th, 2011, 2:54 pm

Never even heard of J#.

[Atlantisbase]

posted on July 29th, 2011, 5:11 pm

Last edited by Atlantisbase on July 29th, 2011, 5:13 pm, edited 1 time in total.

Yeah, maybe I'm thinking of J#, both exist though. J# was MSs failed attempt at a version of Java which also used the .NET Framework. That got canned back with VS 2005. F#, according to Wikipedia is still there, so I got them backwards.