Take X

Let's see....

Extra fuck!

Take IX

CRAP!

Take VIII

More information, as the impossible was claimed

Take VII to see what will happen now...

Ah... just a mistake in the error message

Type 0?

Take VI

Or rather return

Illegal property call

Take V

Lacking sense of self

An onto take IV

Fixing a crash in the process

Regenerated ANYWAY

Take III

Malformed #accept line

Take II

Knudde!

Take I

Calculator linked to combat start up

Aha... I see that Godot is not offering C# support.... That could be nice to give it a try, but not for the short term, but hey, I know they support it, and that's cool ;)

Gauge speed calculator.... Contrary to the first version of the game, this will just base itself on who is quickest and who is slowest, making an order, and not a direct agility to setup as the original game had.

RPG Data linked in Hero Compiler

Wow... It works... IN ONE GO!

OF course, what SHOULD BE and what IS, are two different things, so let's get rocking

Take I

Foes SHOULD now be drawn

various

Linked those spots to the ingame Foe End Compiler

Spot generator did work when it came to the calculation of coordinates, but did not create the actual spots

I've added the call to my FoeCompiler in my building script

Time for a break, though!

Shouldn't be too hard, but I've seen simpler things causing cockroaches

The next step will be to make sure the enemies actually appear

It appears that NIL takes all "ground scopes" of the main script and all scripts in imports through "#use" as one big scope, and that was how the false "dupe identifier" errors were thrown.... Not sure what I can do about it, but it's good to know nonetheless...

It appears I'm correct

Take XVI to see if I'm correct

I wonder....

Anyway as far as I can judge at this specific moment everything looks like it's in order...

Real life stuff

And into Take XV

Recompile all foes

Foe compiler should now also take care of generating a "Points" record for Foes holding their HP

Always HP and not Hp

But the crap is not yet completely over

At least no more parse errors

Take XIV

I've written some void code to get past all that, but I really need to find out what I can do to fix that nasty issue!

Dupe identifier my ass!

Take XIII

No force

WHAT THE????

Take XII

that issue

Oh, I made the same mistake TWICE.... Now I see

Fix ignored

Take XI

Case error in compiler

Take X

This crash in the process

Name link up

Do DAMN!

Take IX

Fixed that too

AH!

NOW I don't believe the claim anymore

Take VIII

Directory error

Just as I suspected

Apparently not....

Take VII will show if this all went the way it should

Blue Slime

Goblin

But my JCR viewer appears to confirm this claim

Ah yeah, it appears the enemy pictures are missing (or at least the system claims so, but it should be possible)

Take VI

Put in an empty Draw() method to make at least sure its abstract has been overridden

Replaced abstract GetTeamName

Take V

Recompiled all enemies

missint enter when there should be one

Script doesn't look like it, but, ya never know...

And Take IV will show you if it's NOT ignore this time...

And recompiled the foe scripts

I also fixed the missing name

Fix ignored???

Take III

That's been fixed

Translation misforming in compiler program

Take II

"Reg"

Take I

That's all done, so let's start testing

I first need to feed my cat and get to other real life issues, and after that it'll be testing time

I've linked the foe compiler to the start up script

Miracles DO happen....

Okay, there are really no parse errors...

Devlog issue

Oh, wait, I think I know what's happening.... Duh...

What the hell?

Take II to make really sure everything's alright!

Let's run Anyway to make sure everything is actually loaded at all

Well I'll be... none pop up

Take I

This has not yet been linked, but some parse errors should now definitely be visible if they are there....

So the current task at hand is to make sure they are all removed!

Compiler script set up

I guess the compilation of foes can now truely begin....

Why QuickNIL throws (nonsensical) errors for the quickmeta example is completely beyond me, tough.... But not really relevant at the present time, either....

Some more examples written

???? False data in Blue Slime ???

A big checkup.... Needed every now and then....

See ya!

It's 1:23am... It's time

Gonna call it

The statistics should've been compiled properly

Well let's say I made progress!

Recognizable by compiler now

AI module in compiler

And more shit fixed

Classes which extend fighter must be created with a tagname!

in order to make sure the foe compiler won't crash the game, I've regenerated anyway

Yeah, I decided to do the description too, and I am planning to give Merya a move which allows her to identify enemies...

THAT looks better already!

NOPE NOPE NOPE

foeret.Image = LoadImage("{val}")

ImageLoad

And Friday the 13th has begun... Hopefull that doesn't bring bad luck to this project :-/

DANG!

I guess that with the image file all that is not RPG lib based is out of the way

let's see about the groupless data!

FoeTag -- Parameter for the in-game foe loader

Okay, now we get into the actual RPG module, and that can be a bit of an issue

Okay, let's see what's next.... :-/

It's not as hard as it looks, still it's a bit brain killing ;-/

So far it all works the way it was intended

Experience should be compiled now

Yeah, there I'll store how much EXP you earn for killing a monster

"Experience" field added

Yeah, I really must NOT forget that one, so this was pretty important ;)

I see that "physical" is misspelled in the foe editor... I must not forget to fix that

that "fixes" the issue indeed

Dirty code straight from hell, but it's the easiest way to prevent tons of needless work!

Ah.... The fatal elements is not yet the way it should be I suppose, hahaha....

the default AI data will be properly compiled

Set up a class for foes

How sweet... Kitty seeks my attentions ;)

Also compile if target doesn't exist!

Combat dir generator

A "force" mode is there to do it anyway... Most of all brought in for if files got corrupted or anything!

I've set up a scanner which has to see if a foe file has been modified.... It's no use to regenerate even if nothing's changed!

This will save me some trouble in a later stage, trust me!

I'm setting up a quick way to do some pre-compiling on foes

Right... Now that I see how leafo did things on moonscript when it comes to linguist I guess it's easy... Just add NIL to the yaml script and dump in some sample code, and make a pull request... I feel a bit silly, but then again, the documentation (or lack thereof) did make things so easy on me...

Now I do not feel like copying GINI stuff into the game itself, although it can still be an option.... Well generated code seems to me like the most plausible way to go....

The next stup of evolution in this game will be.... The FOE compiler, and THAT is gonna be a challenge...

my IQ is only above average... I'm not beyond insanity, so don't expect too much of me....

Let's just say I'm too stupid for this....

I'm messing a bit with linguist, but the documentation (or rather lack thereof) is so fantastic I frankly have NO IDEA what I'm doing!

Also updated

Running, as I wanna make sure this remains here

Some things will never be solved by mankind.... Or at least so it seems!

And suddenly without any kind of explanation... it works....

Take XXXII

Let's try.... :-/

If you eliminate all the impossible, whatever remains however impropable must be the truth.... The point is NOTHING remains after doing that, so the project is getting more and more in danger

GJCR confirmed that the picture files themselves are all in order (not a chance in Hell it would be otherwise, but at this point one can never be sure).

That too isn't it (couldn't be, but I must eliminate all the impossible to come to the truth)

Take XXXI

And let's set the party bar on mute

The arena

Okay, removing the Arena does indeed not make a difference... This confirms what I suspected that XNA's own (dreaded) layer system could not be the cause of all this

Take XXX

Oh... false start....

Take XXIX

Let's temporarily mute some code, and see what happens (shouldn't change anything, but at this point I'll try ANYTHING!).

Nothing spectecular happened... Wasn't to be expected (when there's nothing wrong, there's nothing to be fixed, but yet, the system DOES refuse to do what it has to do).

Take XXVIII

I can NEVER do quick stuff right in once!

Take XXVII

Running compilation script

Small adaption to NALA

However I don't see that on screen, so something MUST still be wrong...

All data produced is in order

Take XXVI

Hmmmm

Take XXV

DIRTY DEBUG STRAIGHT FROM HELL!

Screen is big enough, so that ain't the issue

Take XXIV

Still no clue

Take XXIII

MOAR investigation

Take XXII

Let's try THIS!

Still no good?