Utilities: Temporal Flux v3.00 Release

[RHDNBot]

Update By: Geiger

Several massive code rewrites later...

Temporal Flux 3.00

From the release notes:

New

• Loc Events . Several events can be launched from the prompt.  Separate entries by commas, and sequences by dashes or colons.  Don't open too many (80) at once though; it will use a lot of system resources.
• Loc Events, Loc Maps . When launched from a Location Map, event commands with map coordinates will display their location on the map.
• Custom Data . Users can now custom define data, which can be imported, exported, and mark off freespace appropriately.
• Saving . Mark All Modified added to File menu.  Use this to reseat data records in large patches.  Use sparingly though, as it takes 15+ minutes to save.
• Plugin System . See the Temporal Flux Plugin Architecture documentation for more information.

Fixed

• Loc Events . Cut (Ctrl+X) corrected for new string handling
• Loc Events . Dialogue could be displayed incorrectly in game due to spacing issues
• Compression . Compression tool no longer adds junk bytes onto end of data
• Strings . Setting all strings to dupes no longer crashes the program

Changed

• Loc Events . Decode for Draw Geometry
• Loc Events . Consistent decode between Textbox and Decbox
• Loc Events . MemCpy2E changed to ColorMath
• Loc Events . Partial editor rewrite, focusing on command display
• Overworld Events . PCSub (OEC 08) now decoded and updated to match moving code.
• Saving . Major rewrite of the save system, changing internal aspects of the entire program
• Treasure . Changing the treasure type is now considered a data-changing action.

Between the custom data and the plugin system, the future can only refuse to change for so long.

RHDN Temporal Flux Page

Relevant Link: (http://geigercount.net/crypt/index.html)

[DarkestOmen]

can I ask a question ?
why do you continue to update and perform Temporal Flux,if there are few manuals...=?
I think that only a group of people really know to use TF.
I never understood this (why there are few manuals of an editor and the creator continue to
perform it),tell me why !

[KaioShin]

Continue to update? This news is 2 years old. After a C&D Temporal Flux has been discontinued AFAIK.

[Mauron]

After a C&D Temporal Flux has been discontinued AFAIK.

After the C&D, Geiger announced he intended to continue working on TF despite that. He's also been helping me write a plugin for it recently (planned beta 2 to be posted here as soon as it's ready).

As for manuals, a new one is desperately needed. I'll contact some Chrono Trigger hackers I know and see who is interested in pooling knowledge for it.

[Geiger]

why do you continue to update and perform Temporal Flux,if there are few manuals...?

I have a limited amount of time to work on Chrono Trigger editing.  I can either write manuals or further enhance the editor.  I always choose the latter.  I leave it up to others to write manuals (all existing Flux manuals were written by someone else).

I strive to make the interface user friendly, but at least some of the onus is on the user to raise their level of understanding.  It is not a tool for first time hackers.

After a C&D Temporal Flux has been discontinued AFAIK.

I never received a C&D.  I would ignore one if I did, since nothing my program does is illegal or infringing.  The next release will have a copyright screen pointing this out.

The reason Flux has not been updated in two years is largely because of the following reasons.

- I no longer have a beta team.  This makes everything much, much slower.
- I have had major server problems that have still not been fully resolved.  While I can technically code without the server, its not something I care to do.
- The approach to projects has been radically altered requiring major internal rewrites.  This is a natural consequence of the changes made for the TFPA in the last version.  I expect this will be the last major rewrite and the first version of the code I feel is useful, thorough, and generalized enough to show others.

[Mauron]

- I no longer have a beta team.  This makes everything much, much slower.

If you need help with beta testing, I'm sure many at the DBT would be willing to help however they could, myself included.