SMJS @SMJSGaming

23 | I modify games in my free time. Discord: @smjs Joined February 2019

Tweets

776
Followers

657
Following

43
Likes

286

SMJS @SMJSGaming

3 days ago

@Pentti287991 Also to be fair I do consider it an object filtering issue since there's no reason to constantly check this on something static and can easily be simplified with a filter list.

0 0 1 29 0

View Details

SMJS @SMJSGaming

3 days ago

@Pentti287991 It's about 30% of the step handling in an object dense level. The rest mostly gets contributed by triggers.

1 0 1 35 0

View Details

Fun fact of the day #GeometryDash. Whenever you collide with an object, every single step GD will check over and over and over again that the same object won't suddenly kill the player... The log on the left should show how significant this is. The method behind it is huge.

10 4 255 13K 53

View Details

SMJS @SMJSGaming

3 days ago

@Pentti287991 This is the method I'm referring to: gd-src.undefined0.dev/libcocos2dcpp-…

1 0 0 128 0

View Details

SMJS @SMJSGaming

3 days ago

@Pentti287991 The problem is that it doesn't check *if the collision safe*, it also checks every possible way the player can take damage from any object and if it's relevant for that object. Back to MC terms, it'd be checking if a dirt block is a zombie, creeper, dragon, etc..

1 0 0 134 0

View Details

SMJS @SMJSGaming

3 days ago

@Pentti287991 To put it in terms of another game: It's as if minecraft checks every tick if the object you are standing on suddenly changed into a cactus. Except this check is a 1000 line method handling every possible way you can take damage in the process.

1 0 2 185 0

View Details

SMJS @SMJSGaming

3 days ago

@Pentti287991 Normally you try to rule out static stuff ASAP. What didn't kill you the last 100 steps won't suddenly change when the object is the exact same spot. The best approach would be to flag an object as safe as long as it's static and still being touched by the player.

1 0 4 379 0

View Details

SMJS @SMJSGaming

3 days ago

@ethanph65389124 It's a Geode setting. The log itself however is me just hooking the collision detection and reporting that to the object instance I was colliding with which had a custom log.

0 0 2 319 0

View Details

SMJS @SMJSGaming

3 days ago

@gyjfhugd Ye, I just made a custom object with the cube 001 texture and set the object type to slope 😅

0 0 2 75 0

View Details

SMJS @SMJSGaming

4 days ago

I can complete this level without jumping once. #GeometryDash

3 1 47 2K 4

View Details

SMJS @SMJSGaming

4 days ago

@zAlphii No

0 0 8 2K 0

View Details

SMJS @SMJSGaming

6 days ago

#GeometryDash Object-Collab v0.1.0-alpha.1 is finally out! This is an API to allow mods to make all kinds of custom objects & triggers while being able to work together. This should make gameplay mods extremely easy from now on!

1 0 21 1K 3

View Details

SMJS @SMJSGaming

6 days ago

@TriDeapthBear The treatment is better than it once was but ye I'm glad it's said. I literally have to run simulated doxxes against myself just to make sure I don't one day wake up with all kinds of private details on the street because someone wanted a feature in my mods.

0 0 13 845 0

View Details

SMJS @SMJSGaming

a week ago

@Sloimay It gets more frequent the higher the object count since it has more batches to accidentally accumulate an error.

0 0 1 73 0

View Details

SMJS @SMJSGaming

a week ago

Another fun fact of the day #GeometryDash. Ever had your game fully freeze when loading a level? Well that's because for some reason Rob loops loading levels and on rare occasions the loading progress can land on 0.99998 due to a floating point error. This makes the loop infinite

8 24 405 11K 38

View Details

SMJS @SMJSGaming

a week ago

@Sloimay It tries to batch load what it can per frame so it's based on the processing power/speed of your CPU. That changes easily and thus it's not deterministic.

1 0 3 181 0

View Details

SMJS @SMJSGaming

a week ago

@inruToAHundred From talks I've had with rob... there's a non zero chance alcohol was involved.

3 6 104 2K 6

View Details

SMJS @SMJSGaming

a week ago

@GDmaya_3 They are due to the allocation of unrelated properties per object since the GameObject class serves as a fit all class rather than a base class.

0 0 3 207 0

View Details

SMJS @SMJSGaming

2 weeks ago

Fun fact of the day #GeometryDash. Every object in GD is so unoptimized that it takes roughly 1-3Kb of memory per object. This sounds little until you realize that levels often have 10s of thousands of objects if not far more.