Katie V

It's possible that the CoH successor being discussed on the Titan forums could do something interesting with it (not a straight-up character import, though), and there's a good chance that someone will come up with a "display your character" website that can use these exports.

What version of MacOS are you running? IIRC, "unknown required field load command" errors are caused by bugs in Apple's methods of compiling software for older versions of MacOS.

There are some unconventional ways, but last I checked, the post about not discussing them was still there.

Nothing nefarious here, it's just a side effect of how the patching system works. Patches are sets of instructions on how to modify the game files to get from one version to another. There are hundreds if not thousands of past versions of the game, and generating patches for all of them would take months and require terabytes of storage. Instead, they just generate patches for the versions that are likely to be encountered. Right now, there are patches for what looks like Issue 20.5 and newer, plus specific versions of Issues 1, 2, 3, 4, 6, 10, 12, 14, and 18. You're upgrading from a late version of Issue 20, and the error message is telling you they don't have a patch for that specific old version.

(There is a way they could generate patches that would let users upgrade from any prior version: each patch is strictly an update from one version to the next, and upgrading from an ancient version to the current one means applying all the in-between patches. The problem is that this shifts the burden onto the end user: as many patches undo or over-write each other, the resulting unnecessary work would cause updating from an original install CD to take weeks, and download gigabytes of useless data in the process.)

If somebody's found an activity with a disproportionate risk/reward profile, the proper response is to fix the activity and roll back the rewards. No further punishment is needed -- just letting it be known that you can't expect to keep your ill-gotten gains can act as a deterrent.

Because it is. I've researched CRC32's weaknesses as part of my job: I wanted to use checksums to verify every file making up a software installation, including the file containing the list of checksums, which requires being able to easily generate a file with a desired checksum. I'll send you the details in a PM, but in short, one of the weaknesses permits someone to undetectably modify the file even without knowing the details of how the checksum is computed. Cryptographic hashes were invented for a reason, you know.

Odd. The apostrophe is allowed in filenames on every filesystem that Windows supports, and I didn't have any trouble exporting characters with apostrophes in their names.

Did you pass the "-renderthread 0" command-line parameter? Multi-threaded rendering works on Windows, but it doesn't work on Linux, and I suspect it won't work on MacOS.

The export tool works fine for me with Wine 1.4.1 on Linux.

As I recall, there was an outhouse in the Hollows with the same issue. Porta-potty to anywhere!

120Hz minimizes frame lag if the monitor's controller is up to the task (a cheap or overly-fancy display controller can introduce several frames of lag), but TN panels have annoying color shifts if viewed off-axis, and many of them get their speed by reducing the number of distinct colors they can display. Flicker is only a problem for CRT monitors; LCDs don't flicker at any refresh rate.

The main tradeoff with LCDs is speed vs. color quality: TN panels are fast, while IPS panels are almost as good as CRTs for color.

A typical computer has four states it can be in (omitting minor details like standby power, reduced-power modes and the like):
1) On. Everything is powered up and ready to go.
2) Sleep. The CPU, hard drive, and most peripherals are powered off. Memory is kept powered up to retain its contents.
3) Hibernate. The contents of the memory have been saved to the hard disk, and everything has been powered down.
4) Off. Everything has been powered down without preserving the contents of memory.

As far as your computer's hardware is concerned, there's no difference between hibernate and off. Hibernate/off vs always-on is a different matter, and there's a lively debate over which is better for the hardware (in short, an on/off cycle causes one type of damage to computer chips, and always-on causes a different type of damage). It's quite clear which one's better for your power bill, though.

Unless I've missed something, you can't set Freezing Rain on fire. The fact that you can ignite OSA makes a huge difference in the mechanics of how the powers work.

The rules are quite simple: for a given character, running the WST will grant a bonus the first time they run it; the nature of the bonus depends on if the character is level 50 at the time of completion or not. Eligibility is reset every time the WST changes, so you could have, for example, run the Apex TF on Monday evening for a bonus, then run the Yin TF on Tuesday morning for a bonus. There is no way to get a second bonus for a given character in a given week, and nothing you can do will prevent you from getting the first bonus from the WST.

Pets are immune to the pink patches in MoM, and are reportedly highly resistant to the blue patches in Apex.

I've successfully run three accounts at once on a quad-core Q6600 with 8GB RAM and a GeForce 5770 GT card (a computer that was top-of-the-line five years ago). The limiting factor here was RAM: I could probably have fit a fourth account in, but I preferred to leave room for disk caching, which greatly reduces loading times. I'm fairly sure the graphics card was overkill, as I've run two accounts at once on a much weaker GPU.