Sparky's Eschaton Plugins 4.1 (made for Eschaton 0.8.1.1)

[Sven]

This party sucks, where's the booze and strippers?

[TaxiService]

all in my pants.

[Monk34]

This project is already pretty much epic. What will it become when it's finished?

[Mota-Lev]

WHY DO YOU HAVE CAPS LOCK ON? IT'S NOT EVEN THAT LATE YET AND YOU ARE DRUNK FROM SLEEP DEPRIVATION OR SOMETHING.

I KNOW, IT'S WIERD, RIGHT!?

MAYBE IT'S BECAUSE I COULDNT WAKE UP UNTIL 2 PM TODAY!

LOUD NOISES!


Also, I DON'T KNOW WHAT WE'RE YELLING ABOUT.

[Kayar]

I love... lamp.

[Sparky]

Guerilla was not made as well as it could have been, because often times, the text does not fit on the screen. (You would get an error in XCode if you were to have the same issue.) I noticed this problem in over 30 different tags.

For example, in the globals tag, the Weapon List struct has the name

Weapon List (Update_Weapon_List

while in the plugins that include this information, they only display that information which fit in the default text space on screen in the Guerilla application, which is

Weapon List (Update_

which probably looks familiar to you if you were using the start plugins. It seems that Conure only read the information from the screen and didn't know how to discover the text that was occluded by the interface.

What I did to solve this issue was to export the tag information to a text file (Guerilla lets you do this), and then read the information from that file, where it FORTUNATELY has the entire text block contents. In the case of the above example, I am adding the ending parenthesis, since we don't use scripting anyway (I think this refers to scripting). So it will appear as:

Weapon List (Update_Weapon_List)

You'll notice that Eschaton has a similar issue, but you can always adjust the view of the areas or simply click on an item, do command-C for Copy, and paste the text into a new text file. You could also open the plugin and read the text, if you wanted to do that. So we have options, while Guerilla FORTUNATELY lets me export the tag data to a file... so I'll include these corrections where they apply, and we'll be all set.

EDIT: UNfortunately, the bitmask information is not exported, only the value. So with flags, which are very often occluded by their box constraints, all bets are off (disappointing, I know).

[Mgalekgolo]

u saying that there are no flags????

[Sparky]

I am saying that when you export the tag in Guerilla to a text file, any flag information (Bitmasks) is stored as the value, like 64 for the last item of a long Bitmask, rather than the name, which might be something like "Is Not a Pathfinding Obstacle". So in the application, if it read, "Is Not a Pathfi" and I wanted to figure out what the rest of it said, I would be out of luck, because that info isn't available in any way. I would need the application's source code; even this text is not found as ASCII letters in the data fork, so an application like HexEdit would not reveal the text itself.

[Sparky]

OK, I need your votes.

The globals tag has lots of extra zeros between sections, and the tag itself is rather long. So do you want me to include those areas where it is probably just extra 00's as "Test Me #", or do you want me to omit all those places that are probably not used? They might do nothing, they might break the map (which is unlikely), or they might do something crazy. They most likely don't do anything, but tell me now whether you want me to include these or not.

I normally include them and set them to hidden, but as I mentioned before, Eschaton doesn't like hidden entries within reflexives. So either they show up (and there are over 150 of them), or I remove them.

My hunch is to keep them for experimentation, but I don't want to make it more difficult to use this tag type. Case your vote now.

EDIT: Well, I've gotten one vote to keep, and none to omit. Nevertheless, I'm stopping at the 354th float value, as I'm tired of adding these, and they are probably pointless anyway.

By the way, if we actually find that they don't do anything, I'm getting rid of them. They are there for the plugin testers, but I want to remove them if they are a waste of space.

EDIT: Nevermind, I am adding all the extra float values, except for those with which I am absolutely certain will do nothing.

[Modzy]

Sparky needs more haxxing skills because I can pull any cut-off string, including bitmasks, right from the guerilla.exe. There's actually a whole section of data in the application from which you can pull all the visible stings and even some notes on their functions from.

I can find an attribute like "easy projectile error," and it's notes. The note for it, from Guerilla, is: "enemy projectile error scale, as a fraction of their base firing error. on normal difficulty."

[Sparky]

funny you should mention that one, I remember doing it.

But what are you using to get this?

The globals tag is done, with also an unbelievable number of test values that probably don't do anything.
The spheroid tag is intriguing, because it only consists of four bytes of zero. In case you wanted to experiment with it, I've broken it down in many different ways. You should check it out!

With the final release, I will be providing a dummy map that includes my test tags. Feel free to go through and explore all the values, check my spelling, etc.

There will be a contest with the final release, whoever find the secret password and posts it here will get a prize

EDIT: I just realized you could go through the hex and search for the password, so no more contest

[Modzy]

I'm just searching strings in hexedit.
Searching for things like "easy projectile error" will find it. Note that everything is kind of backward-ish.

[Sparky]

I'm using kornman00v20_release.exe and I see only some error messages in the beginning and what otherwise would be considered text gibberish after that.

But, low and behold, Guerilla.exe (the original one) has legible text strings as ASCII, just as you said.

EDIT: I'm going through and fixing any text issues now

EDIT: seems I was wrong about the globals value. It is really:

Weapon List (update _weapon_list enum in game_globals.h)

[Sparky]

Is it just me, or are these getting more difficult as I go?

Those sound tags were totally weird.

If there is something I can't figure out right away, I'm just going to mark it as such and I'll keep going. I can't be spending all these hours trying to figure everything out when there is such a large amount of straight-path work to do. I can burn through this.

Release before the weekend. Probably tonight, maybe tomorrow morning.

[Modzy]

Is it just me, or are these getting more difficult as I go?

Those sound tags were totally weird.

If there is something I can't figure out right away, I'm just going to mark it as such and I'll keep going. I can't be spending all these hours trying to figure everything out when there is such a large amount of straight-path work to do. I can burn through this.

Release before the weekend. Probably tonight, maybe tomorrow morning.

There are many tags whose information is not listed in Guerilla. Sound and sbsp for instance have a lot of such offsets.