Messages

The closest thing I can think of is UHS (http://www.uhs-hints.com/). UHS used to just be a shareware application, but it looks the hints are all available online now too.

You need == for comparison. Try changing your if statements to:

Code: ags

if (player.Room == 2) dCrystals.Start();
if (player.Room == 3) dMPTutorial.Start();

Total time?

[Gribbler]

It's Spell-a-Saurus! Congratulations, Gribbler!

Babar, two loosely connected titles, Spell-a-Saurus being the 'sequel'. You should check it out if you can find it anywhere. It's even rarer than Eco-Saurus. Its gameplay is definitely distinct from Eco-Saurus. Eco-Saurus has you picking up rubbish, this has you spelling words. It's also got PC speaker text-to-speech. Not sure if Eco-Saurus had that.

Your turn, Gribbler.

Another 48 Hours?

It's not Eco-Saurus! Keep guessing.

You're close though. It's the same game series or brand or what-have-you.

Apologies for the blurriness of the capture, but I couldn't find any screenshots or abandonware sites with this gem, just a YouTuber playing through it:



Obscure educational game! Go!

Startship Titanic

Well, if you think that's proper; you then need to fix the compiler appropriately, and reopen/remake the pull request.

I just want to make sure I understand the problem correctly. Managed structs with user struct pointers are bad because the references aren't cleaned up recursively, but structs with pointers that come from the engine (e.g. Character, Object) should be fine as the engine cleans them up when appropriate. Correct? I need to know if I should lock down all pointers or just user ones. Never mind. I just read your GitHub note again. I believe I need to restrict them so that they can't include any pointers.

E: The dumb way is to have a list of offsets for all managed handles inside struct. In any case this means that script interpreter must support some kind of "type description".

Speaking of dumb ways... if you can't solve it, the half solution you proposed on GitHub seems reasonable to me. Disallow non-built-in managed struct pointers inside managed structs. We could then enable them at a later date when we've figured out how to manage them. I know it cripples managed structs, but there's already so much functionality provided by passing in and returning struct pointers. I'd hate to see it shelved. Crippled managed structs also don't do anything bad. They don't box us in for future development.

If AGScript is replaced by a Java-based language, I will stop contributing to AGS development.

Hear, hear. I don't think anyone who contributes really wants that.

Regarding AGS script, I'm not in favour of replacing it for the time being. AGS script isn't just the language, it's the VM too. We aren't reinventing the wheel. We inherited a project that (for better or worse) reinvented it and we're uh... reinventing a few spokes. Ewww, terrible analogy. Point is that AGS script is 90% there.

I'm running into some trouble with my current project and I think it's an AGS quirk. I created a simple test case for it and it seems to be reproducible outside of my game. The problem is that the default .Say() command right aligns text to about 70 pixels from the right, regardless of the size of the speech view. Here are a couple of demonstrative screenshots from my testing project:





To reproduce, create a blank project and set the speech style to "SierraWithBackground", create a speech view for Roger (e.g. the cup) and ensure this code gets run:

Code: ags

		SetGameOption(OPT_PORTRAITPOSITION, 0);
		cEgo.Say("Test left");
		SetGameOption(OPT_PORTRAITPOSITION, 1);
		cEgo.Say("Test right");

Now, I could be wrong, but I suspect it's a bug/quirk/limitation of AGS. I'd like to know if I'm missing something here and/or I just don't understand how left and right alignment should work. If I've misinterpreted things, please ignore this little section below.

Spoiler

Tinkering as I do, I was able to fix the problem by changing line 2283-2284 of character.cpp from:

Code: ags

    if (bwidth < 0)
        bwidth = scrnwid/2 + scrnwid/4;

To:

Code: ags

    if (bwidth < 0)
        bwidth = scrnwid;

This has the side effect that the maximum width of a .Say() speech box is the width of the screen, not 3/4 of the screen, but it fixes an issue later on where "bwidth" is used to determine the auto-sized position of the speech box.

There are several checks later in the code that sanitise the value of bwidth to ensure it has adequate margins from the edge of the screen. Part of the reason why this issue couldn't just be fixed by adding scrnwid/4 to the x-position of the speech box.

[close]

There's now a pull request for the managed object support:

https://github.com/adventuregamestudio/ags/pull/165

I wasn't able to get constructors working in a satisfactory manner without making the code look like Frankenstein's monster. I will attempt this again in the future. I have reasoned that it's not crucial for 'version 1.0' of user-managed objects, and we have enough to test as it is. We can introduce constructors at a later date and enforce bracket notation (e.g. n = new MyStruct() ) only when a constructor is present in the struct.

Regarding the implementation of constructors, I welcome anyone else to try. To be done properly, I think it will need serious refactoring.

That's it! I guess that means it's your turn.

Why did you start a new one, when we are still guessing what Ben posted?

Ben left the source in tact in his imgur post. And also, it's Blade Runner, for crying out loud!

Try this:

I have one lined up. A proper one. Can I go next?

He say you Brade Runner! Ahem, Blade Runner?

Are we going to keep going with the standards document? I know that we've settled on more immediate things for now, but it would be nice to get all of these ideas down and perhaps discuss a draft of how people want delegates or function pointers to work. Delegates would be keeping with C#, but strangely C#'s delegates always result in me checking MSDN to see if I've got the keyword voodoo in the right order.

I was speaking to Calin on IRC about how there are a few traps in AGS for new scripters that could be minimised by the language. For instance, it would be nice to have operator overloading for concatenating strings ("" + "") and maybe type coercion for ints/floats, or even a Number type.

Looks great! The concept is very interesting. Too bad it's only a prologue! I wish you luck with it and look forward to seeing updates.

Ah yes, the X51. The new Steam machine profile. They're nice boxes. I don't know if they compare favourably to a cube, cost-wise, but they're worth it for the look.

Very nice monitors. I approve of the aspect ratio. In terms of monitors, Dell is ehh... not quite NEC or Eizo, but still good.

The Shivah review was nicely written. I hope to read more reviews in the future!