“I won't pull a deltarune on you guys” -whitepatch.

amgilmo wrote:

How does my alt get more attention????
also bump
also what is the team doing rn? waiting for whitepatch again?

-carrier- wrote:

"I won't pull a deltarune (it's team cherry not deltarune :P ) on you guys" -whitepatch.

amgilmo wrote:

How does my alt get more attention????
also bump
also what is the team doing rn? waiting for whitepatch again?

bump

Bump

i got ignored for a bump message

theosa11 wrote:

i got ignored for a bump message

you were indeed seen

Status update on the battle engine. I can't really say anything this time other than “I'm still working on it.” Sorry about that.

-carrier- wrote:

“I won't pull a deltarune on you guys” -whitepatch.

I think we've established that I am, in fact, pulling a Team Cherry at this point. Sorry about that as well

https://scratch.mit.edu/projects/1231727030/


MORE MUSIC
lmk thoughts

BUMP

BuMp

Status update for the battle engine today.
(TL;DR: I'm opening the battle engine to everyone so we can all work on it faster than I can alone)

I was thinking about the biggest problems with the battle engine (thank you Amgilmo for making me think about this!!) and I feel the biggest problem with it is the fact that I'm being way too clingy with it. Thinking back, I think I had this idea in my head that I had to do everything myself and “prove” that I was a good programmer. Those ideas are an issue I've had to deal with my whole life, and evidently still have to deal with.

My solution to this problem is simple: I'm gonna share the battle engine. I'm not just gonna be clicking “Share” and calling it a day though, since that's not gonna help. Here's my plan:

1. Clean up the existing code. There's a few parts of the project that stand to get a bit of cleanup before I open up the project. This isn't really going to be finishing any unfinished scripts, more so making the existing code easier to understand & use.
   
2. Write some documentation. This code uses a LOT of custom blocks. I'd like to have a reference for you guys to look at so you can understand what everything does and know what inputs take what.
   
3. Create a system for development. I'm noticing that the way we're developing is… kind of all over the place. I think streamlining the way we develop into a “task list” of sorts would help us stay more consistent & finish faster. I haven't yet figured this out (I'll make another forum post once I do) but I'll probably have a prototype system for the battle engine so we can knock that out.
   
4. Release the battle engine project. It won't be released in any sort of “made” state, but my plan is for the first 3 steps to supplement combining our forces to get it made.
   

As for how long this will take? Probably not very long! The cleanup should only take 30 minutes maximum, the documentation should take about the same, and the system will take somewhere between an hour to a day. I'll make another forum post when I release the engine. See you guys then!

P.S. I don't want to keep calling it 2.0 since it's really nothing like Turboyeeter's original engine. I wanted to give it a silly and snappy name e.g. “Project Hotdog” or something, but I'd like to hear your guy's suggestions before I come up with something myself. Amgilmo came up with this on the comment thread I wrote this based off:

amgilmo wrote:

T.U.B.E. The ultimate battle engine. Or you can call it “battle engine”, as it'll just be “stick saga” at the end probably, and 1.0, 2.0, and the like will all be obsolete in the end.

Untitled battle engine maybe?

Bump

Shared the battle engine. I left a little bit of documentation & a to-do list behind, as well as some comments in every sprite explaining some important things to know. If you're gonna work on it, take some time to mess with the existing code so you can learn how I did everything! This project is very complicated if you don't understand what each thing is for.

If you've got any questions on what something is for you can leave a comment asking on my profile and I'll try my best to explain it. Also try and make sure to let others know that you're about to work on something so we can keep the chain of remixes relatively straightforward.

Bump
My school blocked Scratch on the wifi
But only for a week!
I know because I can see that.
So expect no bumps from me until wednesday, next week (I'm not even joking, i used my hotspot to load this page, and it took like 30 minutes)

wait until <[current day v]=(5)>
broadcast [bump v]

amgilmo wrote:

Bump
My school blocked Scratch on the wifi
But only for a week!
I know because I can see that.
So expect no bumps from me until wednesday, next week (I'm not even joking, i used my hotspot to load this page, and it took like 30 minutes)

wait until <[current day v]=(5)>
broadcast [bump v]

Don't stress it! You can always just do whatever you want when you get home. Plus, bumping the topic consistently isn't really super duper necessary, so as long as you're still contributing to the project as usual we'll be fine!
Also yo scratchblocks lackin

<(current [day v]) = [5]>

amgilmo wrote:

Bump
My school blocked Scratch on the wifi
But only for a week!
I know because I can see that.
So expect no bumps from me until wednesday, next week (I'm not even joking, i used my hotspot to load this page, and it took like 30 minutes)

wait until <[current day v]=(5)>
broadcast [bump v]

It's ok to not consistently bump the forum.

BUMP!!!!

currently working on more battle themes.

theosa11 wrote:

currently working on more battle themes.

nice!

https://scratch.mit.edu/projects/1237308879/



NEW BATTLE THEMES