Mipey's Forum Posts

  • Thumbs up!

  • Then you have to store object properties globally (or externally, that works too). When you destroy an object in game, flag it as "DESTROYED" so that it won't be loaded again when you return to its layout.

  • I don't exist

    Mipey - Slovenia

  • Or you can make your sprites white, then use the filter to change their color.

  • Though those engines were made with older Construct technology. Construct 99.x introduces new features, such as Z depth and sprite meshing, which should enable a powerful 3D engine. Brave souls needed to explore the new frontier.

  • Well, the idea is to check for obstacle before moving. Before you move right, check if there is a wall (overlap at offset by number of pixels that match the grid size), if there is, don't go there and check other directions.

    I hope that helps!

  • +Does NOT overlap SOLID at (Grid size) pixels

    Go ahead

  • Performance wise, Construct beats Game Maker and MMF by a large margin. You can test that easily.

  • Hmm. Wild guessing here, so don't sue me if it goes horribly wrong.

    You'd need one large text field to display text and one text imput field. Store the text somewhere as lines (whole paragraphs, which would wrap automatically, anyway), then make a text scrolling engine that just adds and removes lines as requested, while keeping everything 'logged'. For that purpose, list object would be immensely useful (not the windows list thingy), but I guess you'll have to make an use of array or something else (hashtable), which means a lot of extra work.

    For input, basically another text field. It would catch keys typed and type letters out - you'd have to do that manually with events, which is quite a bit of work again, but worth the experience - then submit the text to parser at a press of Enter key.

    The parser would then use the text manipulator to search for strings, find key words, spit 'em out. Then you'd just compare them to the context, execute whichever actions are appropriate etc.; if it is not clear enough, spit an error message out or something along lines of "That is a silly thing to do!" or "Huh?".

    So, yeah, you'd have to reinvent the wheel a few times. Such is Construct in its infancy - not many generic plugins that would simplify the work flow. For example, in this case you'd need a list object (to log text) and text input field for DX runtime (not app). That would save you hours of messing with events just to work a couple basic features out!

    Oh, there is Timeline object, maybe you can make an use of it.

  • You are spending a lot of energy on the INI protection. Sure, it grants you invaluable experience, but shouldn't you be focusing on the main project at hand?

    Simple solutions oft prove to be the best. In this case, you can opt to save the INI file with no extension or obfuscated extension (not .txt nor .ini), by doing so you will stop about 80% of players from editing the file. MD5 hashing and such would only stop like 15% of the remaining 20%.

    The 5% will find a way to hack into it in any case - most likely by editing values in memory.

    In the future, as our projects get more serious, we'll want serious protection as well. By then, we'd have a need for encryption of some kind - scrambling the text and using a certain key to decode the content. Perhaps a plugin could be developed for that purpose, who knows?

    Just my two (broken) cents.

  • Turn off scripting. That needs python libraries.

  • Could save it at the start of layout, then set to that saved value when needed. It is called outsourcing, I guess

  • Yes, use variables for parameters, that works

  • Hmm, now that I remember, I am the most creative and motivated whenever I am walking somewhere. Long walks usually produce the most 'creative energy'.

    Which usually evaporates as soon as I sit down and check forums or stuff.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • If function uses parameters, you have to add parameters BEFORE you call function.

    Like this:

    Function: Add parameter 1

    Function: Call Function "function_name"

    +On function "function_name"

    Text: Set text to Function.Param(1)

    ^ this shows 1 in text

    Function parameters have to be added before call!

    Your second image is correct, it makes parameters BEFORE it calls function.