Poll

Did this guide help you?

Yes.
No.

Author Topic: Eventing and You - Basic Default Events Guide  (Read 6659 times)

I'm trying to remember if onBotTouch is what I always used to change the horse datablock to a player datablock, and I'm just being forgetful.

You remembered correctly.

Okay, never mind than. I remember seeing someone on Badspot's server back before the .blb doors update and mentioning "Woah! Badspot has bot events now!" or something like that; I thought they were actual bot events or something like Amade's.


stuff, I totally forgot about this

I gotta get around to working on the op, I need a list of things that need fixed!

list of client special text (for torque) requires you to login?

Quote
eventing and you
God damn eventing has nothing to do with my personal life you loving stalker.



In all seriousness this guide is very nice, good job ike

In all seriousness this guide is very nice, good job ike

Thanks.


list of client special text (for torque) requires you to login?

It does?

list of client special text (for torque) requires you to login?
Click the link
Click 'LOGIN'
Click the back button on your browser
Fixed

Click the link
Click 'LOGIN'
Click the back button on your browser
Fixed

Doesn't work on IPhones.

He should just copy/paste the text into this topic.
Also, the whole annotation thing doesn't work for me and my Iphone.

List of what needs to be fixed/added:
•A glossary of words-like trigger, fire, etc-that are pedestrian for advanced eventers, but foreign to beginners
•A section for "good combinations of events" for input events that work well with certain output events. I can't think of any default examples currently, but the use of a zonebrick and onplayerenterzone vs onplayertouch for games like foot races (the zonebrick is better)
•A section for "How not to spam", where you explain certain event combinations that can cause spam and the work-arounds/alternatives for these events
•It isn't inportant, but something I suggest you do, because it's never been done, is a/are separate topic(s) that explain various event systems for different games, like the store system for TDMs, or good events to use in Fort Wars.  This could be rather beneficial to the general community so we get less topics on how to event stuff
•Better explanations of events using less technical terms, or, as said earlier, glossarizing technical words that are needed, like triggered.

Over all, this is a very good thread, should be very helpful for people


He should just copy/paste the text into this topic.


I'll do it.

Quote from: GarageGames Wiki
The following markup tags are recognized:

<font:name:size>—Sets the current font to the indicated name and size. Example: <font:Arial Bold:20>

<tag:ID>—Set a tag to which we can scroll a GuiScrollContentCtrl (parent control of the guiMLTextCtrl)

<color:RRGGBBAA>—Sets text color. Example: <color:ff0000> will display red text.

<linkcolor:RRGGBBAA>—Sets the color of a hyperlink.

<linkcolorHL:RRGGBBAA>—Sets the color of a hyperlink that is being clicked.

<shadow:x:y>—Add a shadow to the text, displaced by (x, y).

<shadowcolor:RRGGBBAA>—Sets the color of the text shadow.

<bitmap:filePath>—Displays the bitmap image of the given file. Example: <bitmap:demo/client/ui/separator>

<spush>—Saves the current text formatting so that temporary changes to formatting can be made. Used with <spop>.

<spop>—Restores the previously saved text formatting. Used with <spush>.

<sbreak>—Produces line breaks, similarly to <br>. However, while <br> keeps the current flow (for example, when flowing around the image), <sbreak> moves the cursor position to a new line in a more global manner (forces our text to stop flowing around the image, so text is drawn at a new line under the image).

<just:left>—Left justify the text.

<just:right>—Right justify the text.

<just:center>—Center the text.

<a:URL>content</a>—Inserts a hyperlink into the text, which will open the user's browser. In the URL, the leading "http://" is understood. Example: <a:www.garagegames.com>Garage Games Website</a>. When the user clicks on the hyperlink text, GuiMLTextCtrl::onUrl(%this, %text) function is called. Your implementation can do whatever you want, including but not limited to opening the user's browser and navigating to the url.

<lmargin:width>—Sets the left margin.

<lmargin%:width>—Sets the left margin as a percentage of the full width.

<rmargin:width>—Sets the right margin.

<rmargin%:width>—Sets the right margin as a percentage of the full width.

<clip:width>content</clip>—Produces the content, but clipped to the given width.

<div:bool>—Use the profile's fillColorHL to draw a background for the text.

<tab:##[,##[,##]]>—Sets tab stops at the given locations.

<br>—Forced line break.

Hope that helps.

EDIT: RRGGBBAA = hex code; just ignore the AA unless you want fancy transparent text or something.
« Last Edit: November 22, 2012, 04:46:28 PM by Conan »

Hey look it's this thread again :o


This is fantastic. Thank you. You should do VCE next because the only thing I know how to do with it is make it shoot projectiles from my snake.
« Last Edit: November 22, 2012, 08:43:27 PM by ravencroft »

This is fantastic. Thank you. You should do VCE next because the only thing I know how to do with it is make it shoot projectiles from my snake.

I think Evar was working on a more comprehensive VCE manual for you guys.

Update the guide. On projectile hit event has its own special set of targets/outputs.
« Last Edit: November 22, 2012, 09:13:05 PM by Bester Bageler »