Author Topic: What do you wish you had known before modding Blockland? (Read 1203 times)

Platypi · May 24, 2017, 07:02:22 AM

In the spirit of Conan's Add-on Making Academy, I figured it would be good to create another small resource to help those delving into Blockland modding.

In this topic, talk about what you wish you had known when you were just starting to create add-ons for Blockland. Feel free to talk in a general sense, or about specific types of add-ons. Feel free to give more than one tip. Additionally, if you'd like, talk about how and/or why you got started.

Ad Bot · Advertisement

Metario · May 24, 2017, 08:05:30 AM

the code of the default game functions

lordician · May 24, 2017, 09:58:29 AM

Set yourself goals, nothing too large to start with.
Create larger projects (if you do them at all) in small segments that are products on themselves and work from there on out. (kinda like scrum)
While you might want to work on a thousand of (sub)projects at once due to the many ideas you have, you will end up having a lot of unfinished ones which might get you down in the end.
Work out the idea on paper, or type them out!
Get a good idea of what you want before you start.
Of course it can change, but it helps a lot to know what you want beforehand!

Some generic developing tips that i think could be helpful.

Teneksi · May 24, 2017, 08:12:00 PM

That I could use .dump(); to get all the functions and current attributes of tires, springs, and vehicles (especially in the process of tweaking those values)

Conan · May 25, 2017, 12:16:50 PM

default functions, aka decompiled allGameScripts.cs.dso and such. Would have been a massive help when trying to write some things I ended up giving up on at the time.

for obvious reasons its something that I couldn't really expect. I hear there's a new DSO decompiler floating around out there though, that generates readable and compilable code.

Hawt · May 25, 2017, 03:04:01 PM

Quote from: Metario on May 24, 2017, 08:05:30 AM

the code of the default game functions

Platypi · May 26, 2017, 02:27:46 AM

Quote from: Metario on May 24, 2017, 08:05:30 AM

the code of the default game functions

Implying that his is something you know now? How could I get my hands on this?

Rally · May 26, 2017, 03:16:54 AM

Quote from: Platypi on May 26, 2017, 02:27:46 AM

Implying that his is something you know now? How could I get my hands on this?

I would also like to know where to find decompiled .dso code. Though I'm just going to assume most of it is secret on purpose lol

Kyuande · May 26, 2017, 07:39:04 AM

Quote from: Platypi on May 26, 2017, 02:27:46 AM

Implying that his is something you know now? How could I get my hands on this?

For certain reasons not everyone should have the decompiler (if this goes in the wrong hands it could be spread quick or find something bad and abuse it). If you want to know a certain function you can add me on steam

Cr�wn · May 26, 2017, 10:47:39 AM

Quote from: Kyuande on May 26, 2017, 07:39:04 AM

For certain reasons not everyone should have the decompiler (if this goes in the wrong hands it could be spread quick or find something bad and abuse it). If you want to know a certain function you can add me on steam

It might be a good idea to post the function declarations though, so everyone knows how to parent each function. I may do that.

Conan · May 26, 2017, 01:41:21 PM

Quote from: Cr�wn on May 26, 2017, 10:47:39 AM

It might be a good idea to post the function declarations though, so everyone knows how to parent each function. I may do that.

wasnt mocha doing that in that topic a while ago?

Kyuande · May 26, 2017, 01:55:52 PM

Quote from: Conan on May 26, 2017, 01:41:21 PM

wasnt mocha doing that in that topic a while ago?

he meant stuff like function Stuff::dostuff(%stuffObj, %a, %b, %c) so people don't have to search in trace to figure out what they are

FelipeO_O_ · May 26, 2017, 09:42:19 PM

uuh.. the entire blockland "api" i guess?

Also i wish there were a way to tracing variables besides functions.