Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
It's hard to diagnose because it typically shows as blank in the room editor, but in-game can be whatever is resident in your graphics memory.
)
////player.create
y_offset=0;
////player.end_step
//replace
//x+=hspeed
//y+=vspeed
//with
if (o.solid) {
x+=hspeed;
y+=vspeed;
}
if (y_offset != 0) {
y=y_offset;
}
////platform.player_collision
//right after djump = true, add this:
y_offset=other.y-9;
) then you should delete the player's collision with playerKiller/block events, and add an end step event with the code in this engine. The physics are much more consistent with existing engines. I'm going to update the first post shortly with a new version... stand by! ) Big thanks to everyone helping with testing, everything's really coming together!
////////////////////////////////////GMS Results:
begin of step end of step
(282.00, 439.47) (282.00, 439.47) //start position
(282.00, 439.47) (285.00, 439.47) //first step of movement
(285.00, 439.47) (288.00, 439.47)
(288.00, 439.47) (291.00, 439.47)
(291.00, 439.47) (294.00, 439.87) //should have collided here
(294.00, 439.87) (297.00, 440.67)
(297.00, 440.67) (300.00, 441.87)
(300.00, 441.87) (303.00, 443.47)
(303.00, 443.47) (306.00, 445.47)
(306.00, 445.47) (309.00, 447.87)
(309.00, 447.87) //Collided!
//////////////////////////////////GM8.1 Results:
(282.00,439.47) (282.00,439.47) //start position
(282.00,439.47) (285.00,439.47) //first step of movement
(285.00,439.47) (288.00,439.47)
(288.00,439.47) (291.00,439.47)
(291.00,439.47) (294.00,439.87) //Collided! ) I managed to get the collision with blocks working perfectly in the step event, turns out you have to do x=xprevious/y=yprevious at the start of the event, and x+=hspeed/y+=vspeed at the end of the event... go figure. Anyway, after I did that, I changed the collision check like so:o = collision_rectangle(x-5.5,y-12,x+5.5,y+8.5,block,1,1);where o is a variable holding the id of the block if there is one (like 'other' in the collision event). Adding 0.5 to the coordinates actually seems to work, I can walk off all the minispikes now, and only with the correct align! So the question now becomes, is it really worth switching to this arcane collision system in order to maintain a perfect replica of physics, or should we embrace the new way that GMS suggests? Leave me your comments if you have any! ) ) - Seph and I added the in-game GUI display with deathtime to account for this, so hopefully that's not a big issue. Studio goes on sale all the time, keep an eye out and you could nab it for 50% or more off like I did! It's well worth it considering how great of an IDE it is.
Game Maker Studio has a free version, so you can install that to load the project - no need to go hunting for a 
version of GM8.1! but I don't think this is due to sabotage or anything of that sort, this is simply inexperience on everyone's part (schedulers and runners alike). No one wants to be mercy killed, of course! But an estimate should be as accurate as possible. This is actually why I declined Rekt from being in the marathon - there's no possible way to give an accurate estimate for that game! Before you give an estimate, you should run the game multiple times and get a feel for how long it will take you - don't just base it off your old PB from months ago before you stopped running the game. Your estimate does not have room for cushion - every minute you finish under estimate is a minute that could have gone to another run, and another minute we have to scramble to find content for before people get tired of waiting and leave. The only guideline I can give towards coming up with an estimate is to bring it as close to your PB as possible - if your PB is 30 minutes, but it's possible you could lose 5 minutes to RNG throughout the run, then go with 35 minutes. Be smart about it, make your estimate as low as possible and strive to meet it! This is a natural part of marathon streams, and Twitch in general. But the key is to let it flow naturally - let the viewers make it happen, this is actually the one part of the experience they have control over! Some mods were spamming messages faster than the cooldown that everyone else has to abide by, and this kinda robs the viewers of their fun (I'm not making accusations, nor am I angry at anyone at all - this is just hypothetical discussion for next year!). If you were modded during the marathon, it means that you were a runner in the marathon, or that you are a Wannabe, a close friend of the Wannabes, or that you brought something else to the table that has really helped out. That badge is there to help you stand out in chat, to show that you're someone worth looking up to, someone who should be listened to. Please be a good role model!