Things that should mentioned in the manual.

Post reply

❤Follow Topic(4)

0 favourites

4 posts

From the Asset Store

Gif

Spritefont Deluxe

HK$233.09

An even more advanced version of Spritefont that allows you to make all sorts of new things.

skymen

- Asmodean
- - Joined 31 Jul, 2015
  - 18 topics • 929 posts
- 3
- 17 Dec, 2024
- Quote
I stumbled over my second strange behavior that isn't a bug but is nowhere mentioned.

The first was that events in groups are sub-events. This should be mentioned, otherwise it could to lead to hard to find bugs.

The second is that 'set position' does not work with the tile movement. It took me some time to figure out why my sprite act so strange.

It's mentioned here: https://github.com/Scirra/Construct-bugs/issues/7426

but not in the manual.
- lionz
- - Joined 5 Aug, 2013
  - 58 topics • 7,766 posts
- 1
- 22 Dec, 2024
- Quote
Although it's not mentioned I just naturally understood it to be the case, when I started using tile movement I saw that it uses grid positions within its own behaviour so thought ok setting x,y is not going to work for this or is probably not a good idea instead I will use the grid position numbers.
- Asmodean
- - Joined 31 Jul, 2015
  - 18 topics • 929 posts
- 2
- 22 Dec, 2024
- Quote
Although it's not mentioned I just naturally understood it to be the case

The problem is that if I create a sprite I can set the position. This is not possible if the sprite is created. This is inconsistent.

If you use 'set position' in 'on start of layout' the object will move at the start to the position that is set in the Editor. I don't think that this is so obvious where the problem is.

And set position is a basic action not an extra behavior, if it doesn't work with 'Tile Movement' it could be confusing.
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- dop2000
- - Joined 26 May, 2016
  - 140 topics • 12,763 posts
- 3
- 23 Dec, 2024
- Quote
The Tile Movement behavior feels unpolished, I almost never use it.

C3 has plenty of quirks and oddities. Things like OR-blocks, the Else condition, and Trigger Once could each have a dedicated chapter in the documentation.

One recent discovery that caught me completely off guard (although mentioned in the manual) - restarting a layout also resets all groups in the entire project to their initial state. I had to go through many of my projects and replace "Restart layout" with "Go to layout". I still don’t understand why "Reset all groups" is not a separate action.