Now I got the silly idea (as I think this is also something that made Dyrt slow down when you had a lot of characters in your group), to only recalc the HiSpeed when a new turn starts.... Well I gotta see....

The HiSpeed value should now be initiated... However no visual effects will be seen (not to mention it's not even linked yet to the combat call backs)

The debug lines which are no longer needed

FINALLY!

And let's see now!

Swapped the two files

Name confusion

WTF?

And does it produce a satisfying result

New calculation based on data granted to me by Paint.NET

AFGEKEURD!

And let's see now!

Done

The C++ part appears to work now, but the data is outdated, and a new setup is now used, but that is just a matter of reconfiguring

I think I tackled the issue now

I see this is an old format.... Not too much issue, we can handle that, but at least the mystery has been solved

Again, I suppose!

More clarity from TQSG now (I hope)

I've Also altered the y modifier of the gauge in general... the x modifier looks good to me.... Just combine to good things, together, eh?

The Hotspot issue with Wendicka is not to blame in the C++ code, or so it seems... The parsing somehow failed.... I need to sort that one out.

Better,yet not good enough

While the compiler is working I've been altering some tuning values, but I need to test if they got any effect at all.

So let's FORCE a complete new compilation to make 100% sure

But that tells me nothing at all, since we all know that Visual Studio is bugged in this department

VisualStudio says everything is up to date

And Wendicka's hotspot is ignored.... Is the compilation outdated?

As I suspected

Fine tuning configuration is most likely required, but how much and so on can only be deterimined by seeing, so let's go see this!

Gauge icons should now appear on the time gauge

Typos in project files were to blame

Hmmmm

Project change to make sure the combat icon for Wendicka is properly aliased for usage on the combat gauge (otherwise the game would crash on her uniform version).

Well, that will have to do, I suppose

Gauge position init.... The initial positions will be influenced by the chosen difficulty setting... More player advantage in the easy mode and more enemy advantage in the hard mode... Still the start positions are random, so in the end the start positions can still be in your favor in the hard mode and the enemy's favor in the easy mode, however vice versa is more likely to happen.

The time has come to put Dyrt behind me, and to fully focus on Star Story... I the meantime I am also preparing to move both The Fairy Tale REVAMPED and Cynthia Johnson to Apollo and eventually the same will happen to Sxity-Three Fires of Lung... At the latter will have most in common with TFTREVAMPED, i will focus on 63 later, as there's no need to re-invent the wheel there.

An MD5 hasher is now present... This will make things a bit easier on some departments.... At least I hope so!

(That is, as soon as the beta is live)

I've decided to definitely quit Game Jolt trophy supprt.

I don't see any reason anymore to keep being tied to that platform... as a matter of fact, I want to sever the ties as soon as I can. I will keep the trophies there on for now, in order to allow people to synchronize with a new system I have in mind that I will start on as soon as Dyrt is finished

The works here are going quite well.... Once this is all done, I will try to fully tackle the combat engine here, however for now I just want Dyrt to be done.....

By the way, happy new year!

Temporary standstill.... Dyrt is very close to completion, and therefore I want to have that finished first, so I have my hands FULLY free for this project after that.... So hang on!

(The only reason Dyrt still has the support for this and even GJ exclusive dungeons is because the game is too close to release to remove them now).

For what it looks like now, you can consider the trophy support DEPRECATED! The new version won't have this, and NOT THIS IS NOT OUT OF LAZINESS NOR TECHINCAL ISSUES! This is a choice based on PROFESSIONAL REASONS!

So play the old version quickly when you still want those throphies!

Art for #144 and #274

And I've fine tuned their positions

The Tag-Letters for enemies will now show on the time gauge

perfect

Take XI

let's see

Better, but not quite there

Take X

The errors throws when something works the way it SHOULD work in stead of the not the way it should work

The data looks the way it should look, so that shouldn't be theissue

But proper errors are thrown to the log

Nothing happened at all!

Take IX

At least everything compiles, but that does not mean it also works

That should fix it

TrickySTOI added to the project

It's not yet all cool though as linker errors occur... Clearly I didn't yet cover it all up properly yet

And also done the same with Apollo

I've adapted TQSG to make this all possible

#50 - Nope nope nope - definitely not! But already better than crashing ;)

Take VIII

And fixed it!

I think I got it

Take VII

I've added a more dedicated error message I can see more properly what's happening here

"Nil" value

Take VI

whiner!

Take V

I've voided that issue for now...

It appears that internal definitions in classes do not work when data is delivered by fellow class members.

Take IV

Syntax error

Take III

That's three

Syntax conflict - That's TWO!

That's one!

Take II

It was to be expected this wouldn't go right in one go!

Illegal redefs

Take I

At least I can see if the time gauge appears at all

It will NOT yet work.... For starters the icons and tag letters won't yet appear, and second I need to initiaze all the timers based on all combatents speed values, so we're not yet getting anywhere on that department

And NOW the time gauge should appear

Class link ups (this will not yet make the gauge appear. Only to make it access the fighter table)

Please note, if no errors occur nothing will happen. This because I need to link this up first

I've set up the time gauge... I do not yet expect it to fully work though, but hey the basis is set

The next stop will be the calculation of the speed over the time bar... Although more balancing is in order here too, like in Dyrt, I won't do that... The reason is simple, I want the experience to be the same as the original, and rebalancing the time bar would undermine that, especially since the older setup was not a bug but a choice... Not the best choice, but still a choice. Since Dyrt was completely rewritten and has a complete new experience apart from the story line, this wasn't an issue there

"floating character" in Rayal removed... He was never supposed to be there anyway

All crashes appear to be accounted for

Take XV

ANother bad class call, but of a different kind this time

Take XIV

Another case?

Take XIII

Bad class call?

Take XII

Syntax Error

Take XI

Misreference

Take X

?

?

Take IX

Fucking for the sake of fucking

Take VIII

Some word ik hier zo MOE van!

Take VII

Voided that issue

Crap!

Take V

Missing line

take IV

ID issues

Take III

Lua!=Python, and neither is Neil

Take II

Compatibility conflict

Take I

All I can test here too is the absence of crashes, but that's all

Quick access metatable for Stats and Stat Buffs

Since I only adepted the original Lua code to Neil and the differencies of this engine for this (this because I want the game experience in Star Story to match the original game as much as possible) I don't expect too much trouble here, but, ya never know

Now what is very important to note is that there's no way to know if this actually works the way it should as this is all "under the hood" code. In other words when it doesn't crash, I must assume it works

Compile Raw Data into the actual stats the enemy needs based on its level

WONDERFUL!

Well take VI then to fit all needed formalities then?

Placeholder circle

And NOW it works the way it SHOULD work

Take V

now then?

i thought so

Take IV

There you go!

But now I gotta deal with a file referrence error, but that's looks like an easy one

Apparently that is indeed fixed

Take III

I think it's fixed then

Let's run the crap and see

?

The data is not properly compiled I see.... I will have to investigate to find out why this happens

Syntax error

Take II

linked Lua's "error" function into the main routine, as this is driving me nuts!

GRRRR!

Let's see

The aim circles will still be desplayed. I'll remove them once this works

Anyway, the enemies should now appear on the screen

Now I must hope nothing bad happened to the backup due to that BSOD...

Blue Screen Of Death!

I will backup while Dyrt is running though

After I do more testing work here... Yeah, it really sucks, but I need to sort out my priorities

Next stop... Enemy sprites

Well, what does it do now?

and made sure the X is a bit more to the right

Y position to the middle

Bug fixed indeed, the result is good, but not quite

I think I found the bugger

Stack overflow thorugh by C++ for something that happens inside Lua, eh?

But what is it then?

Ok, I was wrong

Complete crash.... I think I know why this is, but I need to look that up

Let's see, shall we?

these are the hardest to tell if they are right, but as I put in placeholder circles to mark their positions, this should not be that hard.... At least, I hope not

I've set the enemy's automated X and Y postions...

Calling it!

Running

Should be up-to-date, I hope

Take XI

Yeah that was a mouthfull, couldn't think of a better description

C format communication error

Take X

As a result I did have to recompile the enemy set up, oh well

Ah, some old BlitzMax leftover code now leading ot incompatibilities

Take IX

That links it all together

Extract Dir

Compiling

Link API

Extract Dir

Take VIII

Illegal Function Call

Take VIII

Forgotten overrides

Take VII

I hope

Sigh!

Take VI

Oh well

Take V

Code typo

Take IV

I need to fix the bug in Neil about base members in extended classes

Take III

Override error