Since Defold doesn’t yet have its collision information for tiles available to scripting directly (afaik), I’m adding support for tiled importer to get meta tile information for a special layer. Then when moving around games can check meta data for collisions or special things such as spawn rates for mobs.
Going to work on it a while longer before sharing new version.
Delayed function calls on a timer. A proper way to do this is in Defold backlog. It’s been suggested until then to use go.animate. This module by @britzl is better.
local timer = require ("main.timer")
function hej()
print("hej!")
end
function init(self)
timer.seconds(3, hej)
end
function update(self, dt)
timer.update(dt)
end
Searching the site for Defold answers.
With Google, search the entire domain with this
site:defold.com keywords
It will search the public docs and the forum. Remember that Google doesn’t have super fresh results always so if you can’t find answers from that search the forum or the docs directly.
If you want to use distance field fonts be sure to remember to change their material too.
If you forget to you’ll end up with text looking like this.
If you are not using hot code reloading you absolutely should be. It can save you a ton of time when you are working on specific areas of your code without needing to rebuild over and over again. I changed my key map for hot code reload to F2.
Having different screens, loading different screens, switching between screens.
This post references this thread. As well as the official docs:
Think of collections as a way to represent a screen. Main menu, game, splash …
Then you have a central script which loads or unloads collections as you switch screens.
If you would like you could add a super light weight inbetween screen which acts as loading screen -
or have unique light weight loading screens depending on what kind of activities you are going to,
and some screens you go to you may already know they are super light weight and don’t need a loading screen inbetween.
Remember that some screens you may want to not be screens you switch to but ones which act as overlays.
ERROR:GAMEOBJECT: The collection 'default' could not be created since there is already a socket with the same name.
Remember that even in the different screens you may be loading / unloading proxy collections as you need them for that screen.
Below is an example showing how to switch between screens - but as mentioned there are further improvements you can make.
ScreenSwitcher.zip (31.6 KB)
Note that you could use collection proxies at any level. Screens or levels are natural candidates though but you are not restricted to that. In theory you could dynamically load every single object that appears through a proxy—although that is not recommended.
Defining default parameter arguments for functions. This is one way to do it.
function say(msg)
local msg = msg or "Hello" -- if msg is not defined it will be nil
print(msg)
end
say() -- prints "Hello" because no parameter is passed
This style of defining variables is also useful if you have a script which loops that you want to initialize variables once to not be nil without resetting them after they have a truthy value.
local health = health or 0
Sending messages has a cost. Every time you send a message it involves copying and serializing a Lua table. Don’t be afraid to use the messaging system, but try to use it for the right things only. Collisions in systems with many objects for example require extra consideration and optimizations to not overload the message system.
Your on_message functions can also slow down the system depending on how complex that code is. If you are sending many messages it may be this area that needs to be optimized. Use the profiler to see.
Detecting input on edges / corners of the screen. This is very easy to do. You can detect half of the screen for some input and the other half for another. You can detect only the far edges of your screens. Are you using custom rendering? You will want to look at action.screen_x and action.screen_y.
This post by @britzl explains one method for doing this.
Reasons for using this input style: picture book, player movement for a platformer, driving game with steering…
Get current app version to display to your users.
sys.get_config("project.version")
There are many kinds of version number conventions. The way I prefer to do it with my games is 1.0.year.month.day.build so for example today’s would be 1.0.16.4.25 for the first build and 1.0.16.4.25.2 for the second build of the day. I’ve used other systems before but I like this one because you can see when the version was made live at a glance.
You can also use sys.get_config to get anything listed in the game.project file.
sys.get_config("project.title")
sys.get_config("display.width")
sys.get_config("physics.scale")
And so on.
If you are using Tiled to edit your Tilemaps and they’re big, you can quickly create the tilemap file in Defold like this:
Create a tilemap as usual and select the tile source. Select a tile and place it at the origin, then place another tile at a random place, such as 5,5. Save and close the tilemap.
Then in the Project Explorer, right click on the tilemap file and select open with Text Editor. You should see the 2 cell tables for the tiles you added. In the bottom cell set the x and y values of to be how many tiles high and wide your tilemap will be. If you have extra layers, add the values to that as well.
This should make your tilemap the right size for the import.
Well it worked for me 
I’m not sure whether this feature flew under everyone’s radar or not, but we re-did the search mechanism a few weeks ago – enabling filtering of your search results. It’s also more liberal nowadays with displaying words inside of articles, etc. Don’t hesitate to PM me if you have any site feedback or find any bugs!
Do not worry this thread is not forever dead… after I finish the book I plan to continue posting more tips! I’ve been making many interesting discoveries and tricks that may not be immediately obvious and found some things which are usable but not documented at all!
Great. Please post any lacking documentation and we’ll fix that.
Demonstrating the various easing equations built in with how they work with go.animate
Working on this for the book. Run this example, and press up / down to go through the different easing equations. Then left click to animate the Defold logo to the new position. Ghosts of the Defold logo are created as it is repositioned by the animation to so the path clearly, and a white dot is left at the original position to more clearly show how some of the easing equations differ.
I plan to improve it, such as having a mode for the logo to move around randomly within the space after it completes each animation. Todo…
Web version: https://www.bookofdefold.com/examples/DefoldEasingEquations/
EasingEquations.zip (18.6 KB)
Nice! Thanks for sharing!
I just found this and it made my day - I’ve been trying to get the low-res font in Labyrinth to filter by nearest for a while and I put it on the back burner, now I can fix that!
f.lux will cause any Defold game (well, probably the entire screen) to stutter during the transition to “night shift”
Configuration settings retrieved with sys.get_config() are returned as string values; if you’re reading something that needs to be treated as a number (such as display height), use the Lua ‘tonumber’ function to convert the string into a number:
tonumber(sys.get_config("display.height"))