All files removed for now. See below.

Nice work, but is it really necessary to replace all the original core files? Q5.4 is alpha so there will be changes every week in core files. Then you (and every game author) must change your lib_core files again and again. I am changing only some core functions for my game, but with every release of Quest I have to adjust some of them again. If you don't do this, your game will break and can't be played.
So I think it would be better, if this features would be included into the core files. Please write an email to Alex and ask him if he likes to see this features in Quest. If so I could help you to insert them into the core files

Pertex wrote:...
So I think it would be better, if this features would be included into the core files. Please write an email to Alex and ask him if he likes to see this features in Quest. If so I could help you to insert them into the core files

That sounds like a good idea...
But would I still be able to edit the files after I add them?

P.S. Where do I find Alex's email?

Sora574 wrote:
That sounds like a good idea...
But would I still be able to edit the files after I add them?

It's open source so everybody can edit the corefiles. You can create a fork of the code in codeplex, change the files locally and then send a pull request. If Alex thinks it's ok he will merge your code into Quest then

Sora574 wrote:P.S. Where do I find Alex's email?

alex@textadventures.co.uk

Oh ok that makes sense.
And thanks, I'll email him about it

Or instead of that, you could combine these into a new extension, like Chase (of the Wearables library) and Pixie did.

sonic102 wrote:Or instead of that, you could combine these into a new extension, like Chase (of the Wearables library) and Pixie did.

This sounds interesting...
But first, what's an extension and how is it used?

I think an "extension (?an old computer term maybe from the early mac days?)" = library

while, if the feature is good enough for Alex to implement into the actual core engine or library, you can always just make your own (core or a part like a magic system ), via libraries.

there's lots of info on how to make libraries, on the wiki.

but basically, all you do is this:

<library>
  (your created game code)
</library>

this then enables you to within another game (in~by the GUI~Editor), to add this library file~coding into other game, ready for you to use. So, you don't really need to have Alex change his core engine, as you can create your own (well cores and coding parts anyways at least, though I suppose you could probably make your own engine too as Alex made the entire quest program work as objects so I think this would enable you to code your own quest engine using the quest engine Alex already has, which is how I think he changes~updates his quest program himself. Though I'm a noob and could have this completely wrong, need to ask an actual programmer here or Alex, lol) with libraries.

Oh... no, I don't think that could get it done.
See, part of how the guns and armor works (so you don't have to recreate the scripts every time) is that the scripts are set into the 'take' command. Same with 'drop' and 'use', all of which are in the CoreCommands.aslx file.
However, if you could think of some way to get the scripts in the library to override the normal commands, or at least run before them, then it could work.

EDIT: Pull request sent for review. The libraries above also don't work with the Beta, so I'm going to delete them for now. Hopefully, if the pull request is accepted, I shouldn't have to post anymore files here.