Blizz-ABS Bug and Suggestion Compilation

[LiTTleDRAgo]

no!!! You Don't Get It!!!!! It's Very Hard To Tell You Verbally But I'll Try 2 Find 4 A Pic 2 Effectively Describe It!

ALL RIGHT! The Hit Is Something Like This

Spoiler: ShowHide

The First One Is A Normal Thrusting Power.
The Second One Is My Suggested Shot!

for me it just look like flail type weapon with exploding effect 

[winkio]

I get it, but it won't happen until after I make multi-body enemies

[megaman30796]

what do u mean by multi body enemies?

BTW: @winkio Thanks B'coz U Understood it and no thanks 2 the others B'coz they make me have a hard time trying 2 explain

[G_G]

Multi body enemies as in say you have a boss. It is a giant scorpion with 4 legs. Now it has a main body and 4 seperate legs. Each limb is something you can attack and destroy.

@winkio: I can't wait for the create enemy events and the event editor itself. Nice job!

[The Niche]

Couldn't you just make five enemies? Or is it like attacking one enemy hurts the whole thing?

[megaman30796]

cool! reminds me of MH

when will multi body be released?(just make a prediction)

[Blizzard]

Or is it like attacking one enemy hurts the whole thing?

This.

I actually made an unofficial plugin in Star G., but I never integrated it into Blizz-ABS. So it's not much work IMO.

[winkio]

when will multi body be released?(just make a prediction)

Idk, I never know when I have time during the semester.  It could be tomorrow, or it could be in May.

EDIT: event tags are now recognized through manual event creation (you can create enemies and whatnot)
EDIT2: and custom sized enemies.  For example, one event can be 3 squares by 3 squares.  Now for multi-body.

[Blizzard]

and custom sized enemies.  For example, one event can be 3 squares by 3 squares.

<3 <3 <3

[winkio]

Blizz, I have a question.  $BlizzABS.pixel is defined by the following method:

def pixel
  return ($game_system == nil ? 1 : 2 ** $game_system.pixel_rate)
end

or basically 2^rate.  shouldn't it instead be 2^(6 - rate), in order to represent the smallest number of pixels the character can move in one step?  Or am I just confused about what this value is supposed to be.

EDIT: Ah, now I get it, it's how many movement tiles fit into a 32x32 tile.  nevermind, I'm dumb   I swear i hit modify

[Blizzard]

Yeah, I went with that logic because most of the passability calculation becomes more intuitive that way. Same goes for movement. I know that I have to move a character $BlizzABS.pixel times to move it across a 32x32 tile.

[winkio]

Alright, took a little detour, but the extra feature is worth it: centered event sprites.  By putting '\cspr' in the event name, it completely centers the sprite, allowing the graphic to match any enlarged hit areas.  It also may just look better for some enemies, so you aren't always attacking their feet.

EDIT: had to do a bit more fiddling, but now you are allowed to make any event any size, and be able to interact with it.  Say you want to make a player touch event that spans a 7 tile wide by 3 tiles tall bridge, but don't want to have to make 21 different events?  You can do it with just one.  NOW I'll move on to multi-body.

EDIT: and multi-body is done too.  Gotta fix up a few things and update the manual before I release.

EDIT: decided to throw in last_hit_by, last_action, and experience modes just because I could.  And because I had already but experience modes in the config app earlier without fully implementing it >_>

EDIT: 2.83 features list:
Fixed bug with Manual Event Creation where event name tags would not process.
Added last_hit_by and last_action accessors
Added Multi-Body Enemies.
Added Custom Event Size using pixel movement
Added \cspr tag to center the sprite and hitbox of events.
Completed Combat Memory system, which keeps track of last attackers and targets.
Added experience modes to give exp only to the actor that made the kill, or the entire party, or both.

[Blizzard]

You sexy beast, you. <3

Now XAS is significantly inferior to Blizz-ABS. <3

[megaman30796]

there's a custom event size! Cool!

so, multi body is done. can the body parts be destroyed after taking certain amount of damage? if not, think of this as another suggestion.

[Blizzard]

You might want to use custom eventing for that or simply not use Multi-Body events but normal enemies.

[megaman30796]

hmmm......the bodies go separate ways and not follow the main.

[winkio]

the concept of multi-body is that multiple enemies are using the same battler.  You have do do all the event programming to make them how you want them.  For example: you could make a head event the main body, which is stationary, and then two fist events which chase after the player and attack it.  Attacking the fists would only deal damage to the head.

EDIT: so pick up / throw objects are next.  Let's go over the details to make sure I'm not missing anything:
1.  objects can be picked up from the map.
2.  picked up objects can be set down.  Some can be thrown, and turned into projectiles.
3.  some objects return to map when thrown.  Others break and disappear.
4.  Some objects can be caught in the air, others cannot.
5.  Objects will have different throw speeds, and cause the character to move at different speeds when carrying them.
6.  There will be an option in the configuration whether carrying an object completely disables ABS controls, of if using an ABS control (for example, attacking) makes you drop or throw the object.

[megaman30796]

if u attack 2 parts at once, u deal twice the damage, right?

[winkio]

yup.

[The Niche]

Will throwable objects have their own editor tab or will it just use the items tab?