Topic: Tip of the Day suggestions

[subspark]

as with the splash screen's tagline, this is something that can be continually added to over time.

The splash screen loads/disappears too quickly for me to be of any tipping use. Incidentally, CJ, are you still considering taking me up on our new AGS 3.3 splash screen I designed for you a couple of years ago?

To refresh your memory:


You should still have the PM with all necessary files/icons, chief!

Cheers,
Sparky.

[Dataflashsabot]

I like this, but I don't like how it shows what's inside the cup.  Removes the mystery

[kconan]

"Always do a test import of one sprite just to make sure it looks ok in AGS before creating an entire sheet of animation."

[subspark]

Huh?  

Agrees about the cup contents, btw.
Sparky.

[kconan]

Huh?  

That was a tip of the day, and not a comment on your cup, which looks great.  Agreed on removing the contents for added intrigue.

[strazer]

I think these tips are very useful for beginners and this thread gives a chance for every user to contribute, so I'm stickying this.

[Mouth for war]

how about something like... "Don't forget to create a Gui called ghotspot for example then add a lable inside the gui and make sure the text for the label is @OVERHOTSPOT@

Could probably simplify that text but I've seen many people over the years asking "How can I have the mouse pointer describing hotspots,objects etc"

oh well...Just a thought keep 'em coming guys

[Dataflashsabot]

"A GUI label with '@OVERHOTSPOT@' as its text will change to the name of the hotspot under the mouse."

[Dave Gilbert]

"A GUI label with '@OVERHOTSPOT@' as its text will change to the name of the hotspot under the mouse."

...

I never knew that.

[Dualnames]

"A GUI label with '@OVERHOTSPOT@' as its text will change to the name of the hotspot under the mouse."

...

I never knew that.

This is a joke, right, I mean, well, this is the first thing I've learned in ags before everything, so well, Dave, this has to be..eh..a joke. Please tell me so!

[Cerno]

Following a recent discussion:

- Some functions work well in cutscenes (e.g. Character.Say()), while others won't make you happy there (e.g. Dialog.Start()). Choose wisely.

Something very nice I just learned:
- Organize your global variables into structs (e.g. one struct per chapter) to reduce the mess that a lot of these variables can create. Exporting a struct will export all its contents in one go. Nice.

Also:
- Character walking weirdly? Check whether its feet are centered in each image of the animation. Add a blank border to one side if necessary.

Edit addendum:
- Character walking weirdly when passing another character in a cutscene? Try setting the character property "solid" to false.