The latter was cosmetic and therefore easy to fix

And the coordinates of the status are bogus!

Status "Death" lights up regardless of the fact if that is accurate

Unneeded #accept clauses

Take VIII

Forgotten fot reference!

Idiot!

Take VII

Global issue

Take VI

Voided that

Dupe identifier, eh?

Take V

....

I should do that in my entire source

Take IV

Right!

NIL != C# and Lua != C# either

Take III

Just forgotten commas

Parse error

Take II

Okay, my previous tests were not valid, because I forgot the anyway generation.... I'm just stupid!

Let's test if that works!

Status changes displayed now when targeting

No more status changes

Take II

Let's go again!

I should've known

Take I

So let's at least test that!

None of this has been properly tested yet, though.... and all I can test for frankly now is making sure no errors pop up in compliation time

The full setup for status changes will come later, however this was needed to make sure death can be taken care of accordingly, which is technically also a status change.... Thanks to metatables I can death turn up automatically whenever HP gets to 0 and also automatically remove it when death HP go higher... This will get things a bit more on the move and prevent bugs.... At least, that's what I was hoping for....

I've set up some great meta scripts in order to do status changes....

It appears to be working here.... Good!

Some work done here!

CU L8ER!

Updated

Updated

Running

(At last)

AND NOW IT WORKS!

Take XXVII

So let's do it a bit slower so we can do it well...

I went a littlebit too fast here

Take XXVI

Oh, wait a minutes.... Let's try this!

Fix ignored.... as a matter of fact, this is even WORSE!

Issue spot

I'm gonna redo that to make sure this is really the case....

But I didn't see the points damage on screen

No more errors, but....

Take XXV

And thus I'm running my compilation script

I must recompile NALA for this

Extra methods to the RPG Points class

Take XXIV

Illegal function call

Take XXIII

Yeah, does that count as a fix?

Forgot to save, doh!

Take XXII

For real now?

Fix ignored!

Take XXI

I don't wanna talk about that!

Code typo

Take XX

Crash

Take XIX

Rounding issue

It APPEARS fixed

Take XVIII

But let's see what'll happen

I gtt it less and less

Take XVII will tell

Did I fix this?

???

Take XVI

Mistyping

Take XV

Self

Take XIV

This MUST work!

I always hate it when these happen

No good

and let's pray

Take XIII

I tried to void that

Lua has begun to see things that aren't there

Take XII

Whiner!

Take XI

Illegal function call

Take X

Illegal class usage

Take IX

The evil has been found, and killed.... I think

Take VIII

Let's see what will happen with this extra checkup line

But now it appears to have found a "nil" value for Executor.... How come?

All parse stage errors accounted for

Take VII

Wrong operator

Tale VI

Ah, NOW I get it!

Huh?

Take V

Accuracy error

Take IV

Many things

Yeah, it would save me time if I did those stupid things right from the start, eh?

Take III

Forgotten declaration

Take II

Declaration typo

Take I

Time to put it all to the test!

A debug line will tell me how much damage has been done, and how much a target het left

Which cannot yet be properly tested, though

Which is now done

And there's still work to be done here too

And hopefully it will go without any crap this time

Running

And here too

I did update this crap though

This has NOT yet been tested, so I ain't got a clue if this all works

Attack + Damage set up....

Accuracy check

Accuracy check support

I'll try to use the old code for this as much as possible... This makes sure the stat balancing is in order

Now that this works I can get onto the actual attacks and stuff...

All clear..... (for now)

Take XV

Case error in Hurt

Okay, I guess that's back on the move.... :-/

It appears to be caused due to a conflict with my backup tool :-/

It appears the repository that is tied to this DevLog has gone a bit haywire

Or Is that my imagination

Things really appear wrong here

Take XIV

Acceptance issue

Take XIII

And that should fix that stoooooooopid action

Established

Of course I forgot to make the Hurt messages visible

still pretty fast but acceptable now

Take XII

Slowed down the time gauge as this was really too fast

The last test was take XI and not IX, but sometimes when my computer lags (like now, due to the backup running in the background) things like key reversal sometimes happens (that or I made a mistake, but the former appears more likely, given the situation).

Works?

Take IX

Flicker stance effect

Take X

Illegal field

Take IX

Typo in code

Take VIII will have to answer this

I think I got this issue covered now, but I cannot be sure

Mesa Back!

BRB!

and purchase the bread I need

I'll first make a backup

And it won't be easy to get that one under control

I think I know why this happens

It keeps repeating itself and will never link through to the execution stage

Take VII

Did I fix that?

Kutverdommeselul!

Take VI

???

I take that as a "no"!

All parse stage errors appear to be accounted for, but does everything work now?

Take V

Unknown identifier

Take IV

Acceptance issue?

Take III

Misspelled groupname

Take II

Unaccepted group due to order of reading

Take I

But for starters I've been linking the (not yet complete) execution group into the flow, and set it to resume the combat afterward... I will need to test if this works the way it was intended

Plus I must also buy myself some bread today

And I'll need to do some stuff on my VS project too, so this will be a bit of complex planning

The plan today, however is to go for the execution of the attack at last, however this ain't gonna be easy, or at least it will be time consuming

Done

I've been doing some work here, which was planned anyway.... This work may help me on this project also, so it is therefore still vital.

It came to my attention that in Windows 10 (at least on my computer) The Fairy Tale REVAMPED runs terribly slow... Nothing I can do about that right now, as my BlitzMax compiler is broken, and the game will require a complete redo in order to get on the move again.....

It will soon be dumped in the graveyard to die!

Void project in original form archived

And the trophies can be used to SHOW OFF ONCE MORE.... and we all think.... FINALLY!!!!

All errors caused during parsing appear accounted for

Take V

needed

Take IV

Illegal class call

Let's redo take III

Interrupted

Take III