Copies of the original XRXS scripts have arrived

[DerVVulfman]

The main home page I recreated for ScriptShelf now has some extra touches added. All viable links within the page that are directed to copies in our Archive now appear blue. Sadly, one is green as it has been lost. The choice of color dictated by the original page those years back.

Meanwhile, the System Plus portion of the archive is near complete with three script TOPICs remaining. I know at least one will come with some add-ons. And the Damage Display Series which revises the Damage Pops has been complete.

Not that this only covers roughly 1/3rd the 'supported' scripts of 2007. BUT looking at some titles, I can hardly think some would take even an hour to translate (unless someone with cat ears... devil horns and succubi wings... or the like... occupies my time ^_^).

There are two topics from the System Plus portion that do not have translations, only the Japanese scripts revealed. This because there seem to be some underlying issues with each one's code.

The first appears to apply elements to weapons unbidden. That is, the bronze sword you may wish to begin now is Bronze Sword.Fire. And the one you might purchase in a shop is Bronze Sword.vs Darkness. This was meant to be part of an upgrade add-on that accompanied it, but that too appears problematic, unable to define what upgrades you wish for your weapons. Of course, each script contains over 1000 lines of code.

And the other? A Slip damage script that has issues applying slip damage itself. However, that may be something lost in translation and could be in reverse, a system that reduces the power of slip damage despite the initial translation of the function.

My biggest bane are scripts that have element tagging or status effect tagging. One has to take care to ensure that instructions are clear about how the feature works, if there are space or NOT any spaces, or the like. Tagging is very specific.

Worse are the aesthetics aspect of tagged elements or states. Now a bestiary or custom script that might suggest what element affinity the armor or beastie may have could have issue with element tagging if care isn't taken to hide custom tags such as "HITS 2Times" that could allow an enemy to strike its target 2 times, or a tag like "REDUCE 50" that reduces damage by 50HP (and you thought I meant 50%, didn't you). Still, element tagging can be hidden. Status effect tagging is a case of UGH. If you have a state that says "SLIP -20" for a slip damage effect, that custom tag is going to appear in battle, either on the enemy in the help window or on the player's battlestatus window. SO ugly.

Yeah, this is a rant about some of the scripts. I'm releasing them, true. But it doesn't mean I like the use of tags, and for clear reasons when it comes to the menu displays. For this, I may include notifications in the threads themselves where tagging is required.