Project NLFFG

[A-Man]

LF2 is almost perfect on its own and can't be better made as a copy.

Really? I think there is a lot of room for improvement.

Things weren't going as u imagined, we decided as majority on story parts concepts and characters. The problem I see here that this wouldn't be a difference btw the new game progress and the one on extlf2.

I hope everyone here realizes that this will probably not end up as they solely imagines. Everyone who contributes to the game has the right to affect the game in a reasonable way.

Don't get me wrong, I admire ur guys motivation and strong will to get this going but I'm feared this will end in a tiny *poof*

Rest assured and know this won't happen as long as I am working. I'd go as far as trying to do some sprites myself if there is a lack of spriters.

Please don't, the way LF2 sprites are just awesome and I think we should continue on this style. If we want to make things simpler we should do it by using Gad's char-generator rather than making them completely different. LF2 sprites look cute and they blend with physics of the game very well and feels more game-ish in my eyes. They even give you some 3D feel in sprite level. It's not known how original LF2 sprites are made but people think it has something to do with vector graphics. I hope we don't go other way since I can't imagine it with pixelated chars...

I've grown tired of seeing the LF2 style personally, but whatever the majority decide. It makes me wonder, would it be possible to modify @Gad 's char-generator to change proportions a bit (and maybe add few extra frames for the walking and basic stuff like punching)?

And about the engine, I think I can make a DCer for it -since I'm highly experienced in this area - but it's not gonna happen before game gets it's first alpha release.

Haha, that would be great =D

So are you guys really that closed to designing new characters?

[empirefantasy]

and for something as crazy as Harry potter's squiddish games

great now that I am remembering, once I created some rules which I applied in VS mode while playing with my sister. You can hit the opponent only once (or combo in air), then it's opponent turn to hit you. Hitting by weapons are not counted.
Also can we build a football/basketball/volleyball game? xD
I hope it will be that much customable xD

[A-Man]

Haha, yes it will be. Such minigames might be very fun to play, but let's not have that be a priority, at least until we get some solid combat XD

[AmadisLFE]

Can I be the "Idea-ist" of this group? No? Okay, anyway, so I only have one serious question to ask, Do you have a pen and paper ready? Is the Data Changing going to be changed in any way? I mean like the Coding and such? if Not then I will join, if Yes I don't think I can join till I learn how to code.

( Considering Data Changing in LF2 isn't all that hard once you get used to it, I don't think NLFFG's Data Changing will be hard. )

[A-Man]

Can I be the "Idea-ist" of this group? No? Okay, anyway, so I only have one serious question to ask, Do you have a pen and paper ready? Is the Data Changing going to be changed in any way?
I mean like the Coding and such? if Not then I will join, if Yes I don't think I can join till I learn how to code.

( Considering Data Changing in LF2 isn't all that hard once you get used to it, I don't think NLFFG's Data Changing will be hard. )

Of course data changing is going to change. We want more mod-ability don't we? Well, we haven't decided whether the A-Engine will be used or will it be another engine (you guys will decide when I can show it), but if it is then:

A-Engine | LF2 General Comparison (Click to View)

A-Engine datachanging (a-engineering as called by @Dragon5 ) is often very analogous to LF2 (naturally, as LF2 was what insprired me to do this in the first place).
For example, here is a fairly basic frame in LF2:

DC-Code: <frame> 123 frame_name  pic: 1 wait: 2 state:3005 centerx: 39 centery: 79 next: 124 dvx: 10 dvy: -5  itr:     kind: 0 x: 0 y: 0 w: 100 h: 100 injury: 100 dvx: 30  itr_end:   <frame_end>

This is of state 3005 which gives the frame no shadows, and if used in a type:3 file, the ball will not fall by gravity. The ball also doesn't go to frame 10 when hit. But "state: 3005" doesn't really tell much about all of this, it just gives an object a bunch of preset properties.

A-Engine:

PYTHON-Code: [f=123] #frame name; not required as its just a comment |NOSHADOW|IGNOREGRAVITY|  img=1 delay=2 center=39,79 x_vel=10 y_acc=5  set_hitbox[x=0 y=0 w=100 h=100 damage=100 x_impact=30] [/f]

(Used a python lexer just to show comments)
Looks clearer I hope.
Instead of states, I let the a-engineers set the properties of their frames. Object types do not exist, and everything needs to be explicitly mentioned using "switches"; these statements surrounded by the "|" characters. There are 10s of these you can mix to give the frame or its components different properties. There exists tags with the name states (named "ai_states"), but these has to do with AI coding.

The 'goto=' tag (equivalent to LF2's "next:") is by default set to @current_frame+1 so that it can be left out in case one is working on a sequence of following frames.

'dvy:' in LF2 misleadingly accelerates the object up or down instead of set its value as a velocity; therefore the equivalent to it in the A-Engine would be "y_acc=" and not "y_vel=". Also, the A-Engine, by default at least, uses an upright y-axis for its coordinates; aka the coordinate system you use in the school's math class:


So to accelerate yourself up, you use y_acc=+5 and not dvy:-5 like LF2.

But in general it's very similar to LF2, and get's rid of the weird preset rules LF2 has. Don't worry ;), you will be able to help.

There are cases where A-Engine can get more verbose compared to LF2, especially when you try to implement a very specific thing in LF2, like hit_fa: chasing which you would achieve instead with the "track_target[]" frame component:

PYTHON-Code: [f=1] #Energy Ball 1 |IGNOREGRAVITY|NOSHADOW|NOBARS|  img=1 center=57,23 delay=2 goto=1  #store screen id of nearest object which isn't of your team and has an id less than 500  set_reg=$target, &get_nearest_obj{@id<500 && <DVZ_ME#3> != <DVZ_ME#4>}  track_target[ |FACEFORWARD| target_id=$target r_acc=2 max_r_vel=10 max_z_vel=3 ] [/f]

Of course this complexity pays off when you try to do something awesome and totally new, like maybe, use this component on a character to set up a z-targeting system ;D

I will try to show some stuff in a video or gifs this week.

[AmadisLFE]

I meant like, is it going to have serious changes, Anyway Looking at the LF2 and A-Engine, it doesn't seem to be too too hard, a few days like 2 or 3 could help me get used to the Dcing Style that will be used, .

[Gad]

Hey just thought of one thing.
Dk if its not inplemented already though.
If the object is being hit with high position dvy it could bounce from ground and fly up a little leaving some spark for a ground hit .it would open new combo possibilities. Also it would be awesome to see charas being stroke down with fast moving ally falling corpses.

[A-Man]

Hey just thought of one thing.
Dk if its not inplemented already though.
If the object is being hit with high position dvy it could bounce from ground and fly up a little leaving some spark for a ground hit .it would open new combo possibilities. Also it would be awesome to see charas being stroke down with fast moving ally falling corpses.

It's possible to do easily without any need of special tags. First, you have the "hit_ground=" tag with which you can set what frame the object will go to if it reaches the ground. In the frame where the character touches the ground, give it "y_vel=-@y_vel*0.75" to make him rebound by 75% of the velocity he had when he fell down.

Possible to do the latter too, by only enabling a hitbox in your flying knocked out frames if your velocity is higher than something:

Code:

#this is only enabled if the x velocity is more than 20.
set_hitbox[x=10 y=10 w=10 h=10 x_impact=10 enable=@x_vel > 20]

I will try doing gifs of the A-Engine doing things from what you asked in the first page.

@V:
Eh, why "however this project turns out"? This will hopefully turn out awesomely, and you'll get to enjoy it together with the A-Engine =D

[Jahvansi]

apart from however this project turns out I realy would love to get my hands on the A-engine, looks realy fun

[AmadisLFE]

Let me give some ideas too, hopefully you have a pen and paper ready will understand what I mean, because not everyone does...

1. Ceilings:
Explanation: This won't be like your Average ceiling which you can go through, it will be like a Solid Object which you can't go through until you break it, functions same way as the ground but it cannot be stood on. ( The Breaking part is optional )

2. Multilevel-Backgrounds:
Explanation: Backgrounds with stairs/ladders/elevators that allow you to go up to a new floor, technically it changes the background for whoever is in the top floor, could be used with the "Ceiling Break" Function to allow one to go up to the roof/different level.

3. Introduction ( Optional Idea ):
Explanation: Heh, did the title Confuse you? Now what I mean by this is like, the character does a small introduction of themselves, in LF2 the character directly goes into the Standing Frames, but the Idea is that the character says something/does something first before going into the fighting frames, kind of like in M.U.G.E.N.

4. Health, Armor, Mana/Ki and Stamina:
Explanation: Last idea that is in my head right now, I saw a small discussion of it, so I decided to extend it further, anyway, maybe we could make Health, Armor, Mana/Ki and Stamina all Configurable? I mean all of the characters will have 500 Health, 0 - 2 armor points, 500 Mana/Ki and I guess like 200 Stamina or so, maybe lower or higher.

The idea is to make it changeable, like a character will have 9001 health instead of 500, or it will have 1 health instead of 500, and or the character will have high armor but lower health or MP, I hope you are getting the Idea.

( I am expecting all those Ideas to be possible in like the A-Engine right now lol. )