next »

[Pineapple]

@Ichigo Jam

That was indeed the problem, it works beautifully now. Thanks much and sorry for doubting you! 

[Pineapple]

The three methods of saving:

Manual Save
The game can be saved at literally any time when the player pauses the game and chooses the Save option. Titan limits the player to saving within a certain directory, but the game can be saved to any file at all.

Quicksave
The game can be saved to a quicksave file at any time when the player presses F7 and loaded back immediately with F8.

Quitsave
The quitsave is the primary save method. Whenever the game is terminated except as it occurs as a result of a script or critical error, the game is saved to a quitsave file, and when the game is started back up it resumes from where it was left off.

[DustyDrake]

Oh god when I entered the third page this scared the crap outta me:

If it changes, it's a creepy venom/pineapple hybrid.

[Pineapple]

I'd like to go over some the currently implemented features, mostly for the hell of it:

Any game object - maps, entities, sounds, and (soon) graphics schemes can be referenced by name or (the functional equivalent of a) pointer. This should make things maximally convenient when scripting, so that whichever option better fits the situation can be used.

Scripts have full access to keyboard input, and functions within an entity's script can be bound to specific keys with several options that are more difficult to keep track of otherwise. (todo: also have access to mouse position and input)

Automatic memory handling: the game is assigned a unique player entity and map data is automatically loaded into and dumped out of memory as necessary. Supposing some game required different behavior, though, it is entirely possible to cause the game to ignore that functionality and implement the memory handling in your scripts. (though admittedly a bit esoteric - it can be done, but the engine really is not designed for anything other than following a single player entity around)

Optional notification and requesting permission of the player whenever the game wants access to a file outside of the application's directory or subdirectories. (this is to help make sure the scripting capabilities aren't used maliciously. todo: regular file read/write access in addition to the more specialized functions already present)

Full drawing access to the screen space. (todo: read what's already there, too)

Gameplay can be recorded and saved as a specialized video file format that can later be exported as a GIF. Along the same lines, both screenshots and tileshots (screenshot but saves the actual contents of the screen instead of an image of the screen) can be taken. (todo: also save the bits drawn onto the screen by the scripts, which are stored on a separate layer)

[Pineapple]

A nice little splash screen thing to show when the game starts.

[Quarry]

dat jpeg

[Pineapple]

unfortunately I seem to find the horrid quality of it endearing

[eyeliner]

I hate it.

And there's no pineapple.

[JobLeonard]

The latter is kind of a deal breaker.

[Pineapple]

dammit guys

[eyeliner]

Sorry to be blunt, but well, I prefer to be straight up instead of beating around the bush.

I can see where you come from by preferring it, but I'd prefer to see an ascii rendition of a scene or a logo. After all, it IS an ASCII engine.

But hey, your call. It doesn't change anything. As long as the engine does what it's supposed to do, I'm all for it.

[Pineapple]

[QuaziGNRLnose]

that pineapple reminds me of bill o'reilly.

[Pineapple]

oh yeah? well your nose reminds me of bill o'reilly.

[Pineapple]

what the workflow looks like:

Map definition (entity highlighted):


Entity's script:


In action:

[TheBreadCat]

I am really looking forward to doing some awesome stuff with that engine :D

[Pineapple]

it's all about the little features:

Previously, file paths were always relative to the script or whatever file they were specified inside. Now, absolute paths (beginning with a drive name) are detected, and "root:" can be placed at the beginning of a path to specify that the given path should be in relation to the game data file directory. (I also intend to add some other prefixes like "drive:" for the current disk drive and "app:" for the application path.)

I am really looking forward to doing some awesome stuff with that engine :D

I am really impatient myself to get it out there and see what gets made

[Quarry]

What is this exactly, a terminal or a roguelike library

[Pineapple]

What is this exactly, a terminal or a roguelike library

Neither.

It's a rather fleshed-out game engine tailored to ANSI graphics. (The graphic limitations are a bit strict, to be honest, but it severely decreases artistic workload and encourages uniquely styled imagery. Also, the decrease in memory and system demands is phenomenal.) The functionality focuses on making it exceptionally convenient to develop adventure games and, save a few features I've yet to fully implement, JRPGs. Though certainly possible, I don't think it would be very practical at all to use the engine to make a rougelike.

Sometime later I may make a variation of the engine which doesn't involve the overhead that hinders its usefulness for types of games that don't follow the certain gameplay style.

[Quarry]

How many pineapple pics you have, every time I check this thread a new avatar appears