Stage's spawning - group - wait Help needed!!

Die_In_Fire

Die_In_Fire

Well-known member
It's a very noob question what I'm asking here, but after two days of not getting the results I want, I gave up  :( so I really need help. I know it's pretty easy stuff (jeez I have more far complex stuff done before), but right now my mind is clouded...

I have done many stages in the past, most of the time I got them workly perfectly, but on larger stages, I got this kind of problems:

- When I spawn the enemies without using wait or groups, they all spawn ok, usually I do this at the beginning to test spawning locations. My problems starts from there: When I put a wait command or try to apply groups, my spawning coords get f**up. This happens with lot of enemies.

I attached the stage, the red lines are the wait points.

This is how I wish my enemy groups:

GROUP 1:
with the wait at 537, I want a group 3 3

Code: 
spawn delay
health  40
coords 330 190
at   313

spawn   linda
health  15
map     10
coords   400 160
at   286

spawn  Roper
	health 15
	coords  30 167  
	map  6
	at 355

spawn  Will
	health 15
	coords  350  153
	map  9
	at  379

spawn  Willx
	coords  332  158
	map  8
	at  400

spawn  Will
	health 15
	coords  330  197
	map  9
	at  410

can someone tell me where to put the group ad wait commands?

-GROUP 2:
with a wait at 1035 I want a group 3 3
Code: 
spawn  Bolo
	coords  335  160
	map  2
	at  540

spawn  Bolo
	coords  330  159  
	map  3
	at  708

spawn  roper #knife
	coords  330  165
	map  6
	at  827

spawn  Will #knife
	coords  330  161
	map  8
	at  881

spawn  Will
	coords  330  202
	map  8
	at  933

spawn  Will
	coords  340  161
	map  8
	at  990

GROUP 3: a wait at 1323, group 3 3
Code: 
group 3 3
at 1300

spawn  Linda
map 	7
	coords  430  168
	at  1305

Wait
	at  1323

spawn  Linda
map	1
	coords  332  186
	at  1323

spawn  Will
map	9
	coords  -30  173
	at  1323

GROUP 4: wait at 1783 group 2 3
Code: 
group 3 3
at 1645

spawn  Roper
	coords  330  179
	map  6
	at  1690

wait
at 1783

spawn  Bolo
	coords  313  165
	map  2
	at  1700

spawn textest
coords 200 100
at	1701

spawn  Bolo
	coords  350  176
	map  2
	at  1702

can someone please help me where to put the group and wait commands on the stage.txt correctly?? thanks in advance.

[attachment deleted by admin]
 
Sort by date Sort by votes
Just tried that here, what happens is that Linda ad Roper appears way after their spawning coords. they appears once the player gets into the wait position. I want them spawned when the scrolls get ito their coords

this is what I did based on your suggestion:
Code: 
group 100 100
at 273

spawn delay
health  40
coords 330 190
at   313

wait
at 537

group 3 3
at 537

spawn   linda
health  15
map     10
coords   -50 160
at  270

spawn  Roper
	health 15
	coords  30 167  
	map  6
	at 355

spawn  Will
	health 15
	coords  350  153
	map  9
	at  379

spawn  Willx
	coords  332  158
	map  8
	at  400

spawn  Will
	health 15
	coords  330  160
	map  9
	at  410

To explain it better: I want the enemies to keep spawning while the player is going to the "wait" point. with the above example, the player got into the wait point, and then the characters were spawned.
I want it like on this video, look at 6:48, the characters keep spawning until he reach a wait.

Double Dragon arcade 1/2
 
Upvote 0 Downvote
I have been having some issues with that as well, so what I'm about to say might not make sense, but I think you should forego the "wait" and "group" commands on the guys that are between scroll stops.

So, if you want thug1 and thug2 to appear before you reach the stop, then add the wait/group commands AFTER them and before the other bad guys.
 
Upvote 0 Downvote
@Mersox and Die_In_Fire: If you're not asking on how to have group active in between waits then the solution will be simple.

Ilu has posted the solution, what you need next is to set wait and group in correct order like this:

spawn  linda
health  15
map    10
coords  400 160
at  286

spawn delay
health  40
coords 330 190
at  313

spawn  Roper
health 15
coords  30 167 
map  6
at 355

spawn  Will
health 15
coords  350  153
map  9
at  379

spawn  Willx
coords  332  158
map  8
at  400

spawn  Will
health 15
coords  330  197
map  9
at  410

wait
at 537

group 3 3
at 0

group 100 100
at 0

spawn  Bolo
coords  335  160
map  2
at  540

spawn  Bolo
coords  330  159 
map  3
at  708

spawn  roper #knife
coords  330  165
map  6
at  827

spawn  Will #knife
coords  330  161
map  8
at  881

spawn  Will
coords  330  202
map  8
at  933

spawn  Will
coords  340  161
map  8
at  990

wait
at 1035

group 3 3
at 0

group 100 100
at 0


spawn  Linda
map 7
coords  430  168
at  1305

wait
at 1323

group 3 3
at 0

spawn  Linda
map 1
coords  332  186
at  1323

spawn  Will
map 9
coords  -30  173
at  1323

group 100 100
at 0


spawn  Roper
coords  330  179
map  6
at  1690

spawn  Bolo
coords  313  165
map  2
at  1700

spawn textest
coords 200 100
at 1701

spawn  Bolo
coords  350  176
map  2
at  1702

wait
at 1783

group 3 3
at 0

group 100 100
at 0
Click to expand...

BTW spawning delay without group is useless.

Also, you don't have enemies spawned at wait locations so you might not see grouping effect there (except for 1323).
 
Upvote 0 Downvote
Thanks a lot. It's not exactly what I wanted, but works. However I have problem with the last group. They keep spawned on the hole at the end of the stage. Where clearly those aren't their coords... (they are not spawned at 1690 1700 etc...)

Code: 
wall   164 148 -37 0 1719 1690 32 107  # Box set left of door 3ero
wall   1851 124 4 0 46 24 23 83
wall  -6  124  4  0  134  147  23  83
hole   1927 207 79 0 151 106 77 83
hole   952 179 34 0 54 23 34 83
hole   842 206 32 0 197 194 29 83

group   100 100
at   0


spawn  Roper
   coords  330  179
   map  6
  [b] at  1690[/b]

spawn  Bolo
   coords  313  165
   map  2
   [b]at  1700[/b]

spawn textest
coords 200 100
[b]at   1701[/b]

spawn  Bolo
   coords  350  176
   map  2
  [b] at  1702
[/b]
wait
at 1783

group   3 3
at   0

group   100 100
at   0
 
Upvote 0 Downvote
There is an error on your code. take a look:

spawn  Roper
  coords  330  179
  map  6
  at  1690

spawn  Bolo
  coords  313  165
  map  2
  at  1700
Click to expand...

then

group  3 3
at  0

group  100 100
at  0
Click to expand...

The last group won't work, because you are giving a AT 0 after using a AT 1700, so the screen isn't at 1700 pixels anymore and the engine try to spawn the entity anyway.

Plus, if they are spawning on the holes, you need to check you positions.
 
Upvote 0 Downvote
O Ilusionista said:
The last group won't work, because you are giving a AT 0 after using a AT 1700, so the screen isn't at 1700 pixels anymore and the engine try to spawn the entity anyway.
Click to expand...

I changed it to at 1783 (same as wait) and nothing changed...

Plus, if they are spawning on the holes, you need to check you positions.
Click to expand...
nope, the position is ok, check the attached map on one of my previous posts. Even changing the wait to at 1483 just dopn't change anything...  :-X
 
Upvote 0 Downvote
no, what I mean is: you can have a "at & group" at 0 AFTER using at 1700.
The values must be crescent.

in other words: if you have a GROUP AT 100, it will group once you reach 100 pixels, Then you use GROUP AT 1700 and it will group at 1700 pixels. Finally, you use...GROUP AT 0 again? But the char won't be at the 0 position anymore.

Got it?
 
Upvote 0 Downvote
that's what I told you, i changed the 0 values

Code: 
spawn  Roper
	coords  330  165
	map  6
	at  1690

spawn  Bolo
	coords  321  185
	map  2
	at  1700

spawn textest
coords 200 100
at	1701

spawn  Bolo
	coords  321  190
	map  2
	at  1702

wait
at 1783

group 4 4
at 1783
nothing changed.

I used the 0 values because BloodBane suggested them, and I'm sure there's a reason for that, BB doesn't do that kind of mistakes.
 
Upvote 0 Downvote
Ilu, there's one thing you need to know about defining at.
For instance,

spawn Roper
coords ...
at 200

spawn Roper
coords ...
at 400
Click to expand...

You won't see 2nd Roper at scrollpos 200,
however with this

spawn Roper
coords ...
at 400

spawn Roper
coords ...
at 200
Click to expand...

when you reached scrollpos 400, both Ropers will be spawned. OTOH no Roper will be spawned at scrollpos 200.

As you can see at only defines where an entity will be spawned however after reaching certain scrollpos more than defined value, entity will be spawned despite defined value.

That's why these 2 settings work same:

wait
at 2000

group 3 3
at 2000
Click to expand...

wait
at 2000

group 3 3
at 0
Click to expand...

Now back to topic, about enemy falling to hole, let's see hole setting:

hole  1927 207 79 0 151 106 77 83
Click to expand...

That means you can find hole roughly from 1927 to right.

Now these spawns:

spawn  Roper
  coords  330  179
  map  6
  at  1690

spawn  Bolo
  coords  313  165
  map  2
  at  1700

spawn textest
coords 200 100
at  1701

spawn  Bolo
  coords  350  176
  map  2
  at  1702
Click to expand...

If you analyzed their absolute spawned coordinate (measured from left edge):

Roper will be spawned at 2020

Bolo at 2013

textest at 1901

Bolo at 2052

As you can see all 3 enemies are spawned after 1927 IOW they are spawned on hole!.

To solve this, either spawn them from left or spawn them early, 200 pixels early should save them.
The former is better IMO
 
Upvote 0 Downvote
Bloodbane said:
when you reached scrollpos 400, both Ropers will be spawned. OTOH no Roper will be spawned at scrollpos 200.

As you can see at only defines where an entity will be spawned however after reaching certain scrollpos more than defined value, entity will be spawned despite defined value.

That's why these 2 settings work same:
Click to expand...

thanks, very informative!!

To solve this, either spawn them from left or spawn them early, 200 pixels early should save them.
The former is better IMO
Click to expand...
sorry that was a very silly mistake, solved!!

thank you very much, I still can't get all 100% working as I wish, but it's a good beginning.  :)
 
Upvote 0 Downvote
Ilu, there's one thing you need to know about defining at.
For instance (...) when you reached scrollpos 400, both Ropers will be spawned. OTOH no Roper will be spawned at scrollpos 200.

As you can see at only defines where an entity will be spawned however after reaching certain scrollpos more than defined value, entity will be spawned despite defined value.

That's why these 2 settings work same:
Click to expand...

Ah, I see. Semantically and logically, is wrong. But if the engine accepts it, ok :)
 
Upvote 0 Downvote
BeasTie said:
Have you read this yet? - http://www.caskeys.com/arc/games/openbor/wiki/index.php?title=Easy_Enemies_Grouping_On_Stages_Tutorial
Click to expand...

Yes, and was the origin of my problems. I wanted to originally spawn enemies when player is walking, but always on group 3 3, but you can use that tutorial with group 3 3 and a maximum of 4 enemies or the wait is ignored.

remember the “Wait At” MUST BE BEFORE the last enemy according to the MAX number in your group,
Click to expand...
Doesn't work with small group with lot of enemies.
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top Bottom