Show Posts

1

Tutorial Collection / [RESOURCE] SECTINFO UDB Scripts

« on: January 01, 2024, 01:29:48 AM »

SECTINFO UDB Scripts

If you've been out of the loop, SECTINFO is a file that can be put into the root of your map pack's PK3 to provide a location name for any given sector in your maps. These location names can be seen in teammate coop info, typed out by using the $location chat command, or queried by ACS. More details about SECTINFO can be found here.

Heavily inspired by Thunderono's SECTINFO tool, this new set of scripts can be used with Ultimate Doom Builder to be able to generate SECTINFO definitions right inside of the map editor.

Additionally, as a bonus, there's extra scripts to easily add callouts to sectors or select all sectors of a given callout. Just like the aforementioned SECTINFO tool, Domination support is here too!

Download Here!
View Repository

Installation Guide

First, open any map in Ultimate Doom Builder. Once the map is open, click the Scripts tab on the right side of the screen.

This'll open a navigation pane where you can view and run all of the scripts you have. Inside of this navigation pane, right click on the Examples folder and click Open in Explorer.

This'll take you to the directory that the Examples scripts are stored within. We'll want to navigate back one directory to the Scripts directory which is the root of Ultimate Doom Builder's script storage, so click the Scripts piece of the directory path.

Next, you'll need to download the SECTINFO scripts, so click the download link here.

Once you have it downloaded, navigate inside of the ZIP file until you locate the SECTINFO folder.

Drag the SECTINFO folder into Ultimate Doom Builder's Scripts directory.

If successfully done, you'll see a brand new set of scripts in Ultimate Doom Builder. Enjoy!

2

Maps / KNDM Map Pack - V2B Released!

« on: August 25, 2023, 10:00:38 PM »

Extus didn't want to make this thread himself, so this'll have to suffice.

KNDM Map Pack

A set of maps designed for Deathmatch and compatible with MM8BDM V6B onwards, created by Extus.

(click to show/hide)

Download V2B Here!

See internal README files for credits and changelog. Contact Extus for any questions, concerns, or comments.

3

Tutorial Collection / [RESOURCE] Can't Believe It's Not SLADE

« on: May 21, 2023, 11:27:08 PM »

Can't Believe It's Not SLADE

Can't Believe It's Not SLADE (CBINS) is a command line utility that allows users to easily create and manage PK3-based projects in more modern editors such as Visual Studio Code rather than SLADE.

It does this by providing the ability to create directory structures that can be opened in modern editors and tracked by source control such as Git, but then also providing the ability to compile that directory (including its ACS) into a PK3 file.

Download CBINS v1.2
View Repository

Screenshot

(click to show/hide)

Basic Usage

(click to show/hide)

Configuration

(click to show/hide)

Commands

(click to show/hide)

FAQ

(click to show/hide)

Accreditation

- Credit to Russel for the original Doom Archive Manager that has helped development so much already and inspired this project.
- Credit to Ken Silverman for creating pngout.exe which this utility optionally uses for PNG optimization when building.

4

Bugs/Suggestions / Bars and Numbers: a New Default UI?

« on: February 21, 2022, 10:47:35 PM »

It goes without saying that a lot of mods and a lot of people have modified the vanilla status bar in some shape or form. The backend for the status bar is seeing lots of reform for v6b API related reasons, so I anticipate that now might be a good time to get some centralized discussion about what works for the current status bar, and what might not work so well.

The current vanilla status bar has unconventional placements, a comparatively cramped design, and segmented bars which create ambiguity in ammo and HP values, but it is unarguably Mega Man in design and holds a charm for many of us.

We've had talks of the status bar in the development team, but without public perception, there hasn't been an easy consensus. So, the point of this thread is primarily to gauge insights on how people feel about the current vanilla status bar, but also to propose three new potential status bar replacements if the current is seen as undesirable, from minor changes to big overhauls. It is worth noting that these are primarily proof of concept, so if you like a certain layout but don't like the style, bring it up! Tell us what works and what doesn't, and especially fill out the survey at the end.

All of the following are being proposed as full scale replacements to the current default UI. While options would be nice, they are not viable for the modding scene, and would be more likely unsupported as horizontal bars often have been currently.

Genesis Flavor
At a Glance

(click to show/hide)

Goals
Genesis Flavor is very simple, as it's the current vanilla status bar, but with different bar graphics inspired by Wily Wars
It preserves the Mega Man layout and style with segmented bars, but removes the black portions to prevent ambiguity.

Download and Try!

Compromise
At a Glance

(click to show/hide)

Goals
Compromise has all the elements of Genesis Flavor, but it also introduces layout changes.
The ammo bar and HP bar are swapped, so that it follows more modern conventions introduced in MM8, MMPU, and MM11.
There is also now a gap between the bars, allowing for breathing room between UI elements.
With the ammo bars extending towards the right, there is more room for additional UI elements.

Download and Try!

Anarchy
At a Glance

(click to show/hide)

Goals
Anarchy, as the name suggests, overhauls the layout completely.
It uses more minimalist MM8-styled bars, contrary to the NES segmented bar.
It provides borders around UI element ala MMX to make things easier to parse.
In horizontal mode, it resembles more closely traditional shooter UIs, by having the HP on the left bottom corner and the ammo on the right bottom corner.
In vertical mode, it is a compressed version of the UI in the top left for previous vertical users.
Both styles are designed to use the same graphics to prevent modding and graphic work overhead.
Anarchy introduces new UI elements, one of which displays which weapon slots you have in your inventory and highlights the one equipped.
Another new UI element is bars and icons displayed on buster weapons which show charge status and cooldowns.

Download and Try!

Double Take
At a Glance

(click to show/hide)

Goals
Changes the bar graphic to use a bar closer to NES style, but still, one that fixes the black segments to avoid ambiguity.
Preserves the current order and general placement of bars, however, spaces them out a bit more to allow room for added elements and better reading.
Implements the weapon slot display of Anarchy and would be able to support buster UI elements.
Implements a mugshot that would change with skin.
All numbers have been standardized to one font which is bigger than all the previous ones, making numbers more prominent in the UI.
Vertical moved slightly closer to the crosshair, primarily more towards the right and slightly down.
For all intents and purposes, this is essentially meant to be the vanilla UI, except with stuff spaced slightly better and important information scaled and placed bigger.

Complete the Survey!

Give any further thoughts in the thread below!

5

Projects & Creative / Trill's Addon Shop - Updated Ping Button!

« on: November 18, 2021, 04:37:17 AM »

(click to show/hide)

I've found myself being interested with the idea of mods that just serve to be general quality of game and play improvements, so here's a few mods I've created that I would consider must-haves when hosting your servers. All the addons in this thread are designed to be interchangeable and compatible with most all mods and modes of play out there.

Damage Display

(click to show/hide)

Map Voting

(click to show/hide)

Ping Button

(click to show/hide)

Side Swap

(click to show/hide)

6

Projects & Creative / Endless Attack - Roguelike Mission Mode

« on: May 25, 2021, 05:50:24 PM »

Time to see who all remembers the Mission Mode layouts,

(click to show/hide)

Endless Attack Mission Mode

The name here's pretty self-explanatory. You get segments of various old Mission Mode maps combined with some new segments into a randomized rogue-like inspired game mode that allows you to collect weapons as you progress towards beating every boss. Segments get more difficult with harder enemy types and potential new layouts as your score rises. High scores and fastest times for each segment are recorded, so go for broke with the lives provided for each run. Defeat a boss and everyone gets a free restock of lives to get right back into the action. It's the classic Mission Mode gameplay just with extended replay value and option for mappers to create custom level segment packs and load them alongside the mod for a larger pool of pieces to fight through. Even programmers can get in on the fun with potential for custom bosses and even more weapons to fight for, so it's the ever-expanding Mission Mode experience.

Screenshots

(click to show/hide)

Credits

(click to show/hide)

FAQ

(click to show/hide)

Quote

Can I play this mode offline?
Yes! All you need to do is load up your files and load EAHUB in Survival Cooperative mode via Offline Skirmish in the menu.

How do I develop new level segments?
(click to show/hide)
Quote
Creating new level segments is relatively painless as long as you're experienced with Doom Builder already and have some basic ACS knowledge. Just don't forget to load the Endless Attack file as a resource so you'll have access to all the enemies within the build.

For the mapping side of things, you'll want to create a teleporter for your spawn point to sit on. All you need is a single SP Player 1 Start placed right on top of it, all players are gonna spawn in this spot and telefragging is disabled, so there's no need for more. For the end of your level, you'll do similar, just this time instead of a spawn point, you'll want to add an "Actor hits floor" activator. It should activate special 226 with a named script of "sp_nextlevel". Just be careful of any spaces else the script won't properly execute.
(click to show/hide)
Quote

Take care when designing your level segments such that they don't feel too daunting with length or difficulty. The standard of play is 3 lives per run, so you certainly don't want your segment to be the de facto run killer. However, make sure to include 1-Ups in your level if you want to encourage players to take risks for potential rewards. Don't forget to include a map card with your map as well, after all, players are gonna need the person to blame for when the run loses.

Once your level segment is finished, implementing it into the Endless Attack segment pool is as easy as a single script. Make sure to drag the EA_MAPS.ACS source file into your own project, so that it can properly be imported into your own ACS file, but don't compile it. Once done, you'll want to create an ACS file that looks something like this TRL_IPRT.ACS,
Quote from: TRL_IPRT.ACS
#library "trl_iprt"
#include "zcommon.acs"

#import "ea_maps.acs"

Script "trill_imports" OPEN
{
Delay(5);
defineMap("TRILL01");
defineMap("TRILL02");
defineMap("TRILL03");
}
This is the file that you'll wanna make sure that you compile every time you need to update it to introduce a new level segment. Make sure to create a LOADACS file as well, with the name of the compiled ACS file, so in this case, it would be a LOADACS file with the line "TRL_IPRT". This tells the game to make sure to load that compiled ACS with every startup.

For a standard level segment, this is where you can stop and all will be well with its introduction. However, Endless Attack offers the option to include an increased difficulty layout for each map. The map variant is created the exact same way as before, but the ACS definition is a bit different. You can see an example of how you'd define TRILL01 and its variant EXTRLL01 in the following code,
Quote from: TRL_IPRT.ACS
#library "trl_iprt"
#include "zcommon.acs"

#import "ea_maps.acs"

Script "trill_imports" OPEN
{
Delay(5);
defineMapWithEX("TRILL01", "EXTRLL01");
defineMap("TRILL02");
defineMap("TRILL03");
}
So every time TRILL01 is rolled for the next map, if the stage is also rolled to be a variant stage, it'll instead opt to use EXTRLL01 as the map.

That's all there is to know for developing new level segments and there's plenty of existing content to reference if any issues are ran into, so good luck with the mapping!

How do I make Sniper Joes stand still?
A few of the enemies defined in Endless Attack have special behavior when you toggle their first argument. Here's a list of them,
(click to show/hide)
Quote
Metool - With its first argument toggled to 1, it'll immediately go back into its helmet after shooting rather than running around.
Sniper Joe Shielder - With its first argument toggled to 1, it'll stand still between firing rounds.
Sniper Joe Grenadier - With its first argument toggled to 1, it'll stand still between attacks. With its second argument toggled to 1, it'll only toss grenades without using the buster.
Time Pendulum - The speed that the pendulum swings at is determined by its first argument.
Hammer Joe - With its first argument toggled to 1, it'll stand still between tossing its hammers.
Puyopon - With its first argument toggled to 1, it'll start on the ceiling wherever you placed it rather than beginning on the floor.
Escaroo - With its first argument toggled to 1, it'll become invincible and only fire bombs around it in a spiral, good for creating a stationary hazard!
Flamethrower Joe - With its first argument toggled to 1, it'll stand still between usages of the flamethrower.

How do I develop new enemies for my maps?
(click to show/hide)
Quote
The main important notes with enemy creation is to make use of the standardization already in place for enemies, otherwise your enemies might feel nonfunctional or out of place. To do this, make sure to inherit your enemy off of "GenericRobot" so that it receives the standard flags that most enemies in the project have. This makes sure that weapons will feel consistent against your enemies and they won't have any difficulties traversing your maps.

Additionally, you'll want to make sure that each enemy you create calls "ACS_NamedExecuteAlways("sp_enemystart",0)" on its first frame, and preferably in a way such that it won't attempt to call the script again to reduce network usage. This script is responsible for multiple things, most importantly the HP scaling for additional players, and the pain feedback for when they receive damage. In the case that you want an enemy to not experience HP scaling, such as with respawning enemies, failing to call that script isn't a proper method of doing that. Instead, you should call "A_GiveInventory("HealthScaled",1)" first, then still proceed to call "ACS_NamedExecuteAlways("sp_enemystart",0)".

For any instance of damage an enemy does, make sure that it is followed by "*ACS_NamedExecuteWithResult("sp_cbmHP")". This script checks whether or not a mod with higher base HP values, such as CBM, is loaded, and appropriately scales the damage so that it matches up. It allows your enemies to be compatible with more than just vanilla being ran with it. Additionally, make sure that it uses a damagetype of "Enemy", "Misc", or "FlingDamage". "Enemy" has standard hitstun, "Misc" has no hitstun, and "FlingDamage" applies a Wind Storm effect to the player. These ensure that your enemy won't be able to friendly fire any of their comrades on the field.

Finally, make sure that you give your enemy a DoomEditor number that doesn't conflict with any existing enemies or props, alongside including "//$Category MM8BDM-Enemies" among its flags. This allows your enemy to be placed into maps and organized into a category with all other enemies from Endless Attack.

For an example of how an enemy should look in this format, reference this Flamethrower Joe,
(click to show/hide)
Quote
actor FlamethrowerJoe : GenericRobot 30039
{
//$Category MM8BDM-Enemies
Height 52
Radius 32
Obituary "%o was burnt to crisps by a Flamethrower Joe."
Health 95

translation "192:192=4:4", "198:198=227:227"

maxstepheight 50
+MISSILEEVENMORE
+MISSILEMORE
+LOOKALLAROUND

dropitem "WeaponEnergy", 16
dropitem "SmallHealth", 16
speed 8
States
{
Spawn:
TNT1 A 0
TNT1 A 0 ACS_NamedExecuteAlways("sp_enemystart",0)
Look:
SNIP A 5 A_LookEx(LOF_NOSOUNDCHECK,0,0,0,360,"See")
loop
See:
SNIP B 1
SNIP B 1 A_JumpIf(Args[0]==1, "See2")
SNIP B 1 //A_JumpIfTargetInLOS("ShieldUp") // THIS FUNCTION IS BUGGED ONLINE ARGH!
SNIP BBBB 1 A_Chase
SNIP A 0// A_JumpIfTargetInLOS("ShieldUp")
SNIP CCCC 1 A_Chase
SNIP A 0 //A_JumpIfTargetInLOS("ShieldUp")
SNIP DDDD 1 A_Chase
SNIP A 0 //A_JumpIfTargetInLOS("ShieldUp")
SNIP EEEE 1 A_Chase
Goto See+3
See2:
SNIP A 1 //A_JumpIfTargetInLOS("ShieldUp")
Goto Missile
ShieldUp:
Missile:
TNT1 A 0 A_SpawnItemEx("SP_SniperJoeShieldX",23,-17,8,momx, momy, momz, 0, SXF_NOCHECKPOSITION|SXF_ABSOLUTEMOMENTUM, 0)
TNT1 A 0 A_SpawnItemEx("SP_SniperJoeShieldFX",23,-17,8,momx, momy, momz, 0, SXF_NOCHECKPOSITION|SXF_ABSOLUTEMOMENTUM|SXF_TRANSFERTRANSLATION, 0)
SNIP A 2 A_FaceTarget
TNT1 A 0 A_GiveInventory("CutterFlag",1)
TNT1 A 0 A_JumpIfInventory("CutterFlag",30,"ReadyFire")
loop
ReadyFire:
TNT1 A 0 A_TakeInventory("CutterFlag",999)
TNT1 A 0 A_SpawnItemEx("SP_SniperJoeShieldX",23,-17,8,momx, momy, momz, 0, SXF_NOCHECKPOSITION|SXF_ABSOLUTEMOMENTUM, 0)
TNT1 A 0 A_SpawnItemEx("SP_SniperJoeShieldFX",23,-17,8,momx, momy, momz, 0, SXF_NOCHECKPOSITION|SXF_ABSOLUTEMOMENTUM|SXF_TRANSFERTRANSLATION, 0)
SNIP A 2 A_FaceTarget
SNIP A 0 A_JumpIfCloser(512,"ShieldFire")
Goto ReadyFire

ShieldFire:
SNIP FFFFF 5 A_FaceTarget
SNIP F 0 A_FaceTarget
SNIP F 0 A_PlaySoundEx("weapon/magmabazooka","Weapon")
SNIP F 0 A_PlaySoundEx("weapon/heatshot","SoundSlot6")
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 0 A_FaceTarget
SNIP F 2 A_CustomMissile("JoeFlamethrower",12,6,frandom(-3,3),0,frandom(-3,3))
SNIP F 15
SNIP F 1 A_JumpIf(Args[0]==0, "See")
SNIP A 0 A_ClearTarget
Goto Look

Death:
CRAZ A 0 A_Pain
CRAZ A 0 A_Fall
TNT1 A 5 A_SpawnItem("EnemyDeathFX",0,32)
TNT1 A -1
stop
}
}

actor JoeFlamethrower
{
PROJECTILE
+BRIGHT
Damage (3*ACS_NamedExecuteWithResult("sp_cbmHP"))
Speed 30
Obituary "%o was burnt to crisps by a Flamethrower Joe."
damagetype "Enemy"
Radius 20
Height 20
reactiontime 1
scale 2.5
States
{
Spawn:
TNT1 A 0
SpawnLoop:
XE01 ABC 2 A_SpawnItemEx("JoeFlamethrowerFX",0,0,0,0,0,0,0,1)
XE01 DEF 2 A_SpawnItemEx("JoeFlamethrowerFX2",0,0,0,0,0,0,0,1)
XE01 F 1 A_Countdown
wait
Death:
TNT1 A 1 A_SpawnItemEx("OilPitIgnite",0,0,8)
stop
}
}

actor JoeFlamethrowerFX : BasicGraphicEffect
{
+BRIGHT
renderstyle add
Alpha 0.8
states
{
Spawn:
XE01 A 0
XE01 BCD 1 A_FadeOut(0.2)
stop
}
}

actor JoeFlamethrowerFX2 : BasicGraphicEffect
{
+BRIGHT
renderstyle add
Alpha 0.8
states
{
Spawn:
XE01 A 0
XE01 EFG 1 A_FadeOut(0.2)
stop
}
}

If that's all you want out of your enemy, you can stop here. However, if you want your enemy to have harder AI and change colors as the run progresses, you'll need to define it as an EX enemy. This is done with some basic ACS definition in the same vein of defining a new level segment. You'll want to make sure to drag the EA_EX.ACS source file into your project, but again, don't compile it, it'll be used for importing instead. Then, you'll want to create a file that looks something like the following,
Quote from: SP_IMPRT.ACS
#library "sp_imprt"
#include "zcommon.acs"

#import "ea_ex.acs"

#DEFINE MACHINEGUNJOE 10500
#DEFINE MACHINEGUNJOESCOUT 10501
#DEFINE MACHINEGUNJOEGRENADE 10502

Script "sp_translations" OPEN CLIENTSIDE
{
Delay(25);
CreateTranslation(MACHINEGUNJOE, 192:192=4:4, 198:198=42:42);
CreateTranslation(MACHINEGUNJOESCOUT, 192:192=4:4, 198:198=171:171);
CreateTranslation(MACHINEGUNJOEGRENADE, 192:192=4:4, 198:198=41:41);
}

Script "sp_imports" OPEN
{
Delay(5);
defineEXEnemy("SniperJoeScout", "SniperJoeScoutEXPackage");
defineEXEnemy("SniperJoeShielded", "SniperJoeShieldedEXPackage");
defineEXEnemy("SniperJoeGrenader", "SniperJoeGrenaderEXPackage");
defineEXEnemy("SniperArmor", "EXEnemyToggled");
defineEXEnemy("MetEnemy", "EXEnemyToggled");
}
The defineEXEnemy function first specifies the actor name of the enemy, then the inventory item to give to that enemy to allow it to take on EX enemy traits. Since Sniper Armors only begin to walk when they've become an EX enemy, they only need the "EXEnemyToggled" flag that their AI checks for. However, you can see that since SniperJoeScout changes color as well, he is given a CustomInventory actor which you can see below,
Quote
actor SniperJoeScoutEXPackage : CustomInventory
{
States
{
Pickup:
TNT1 A 0 Thing_SetTranslation(0,10501)
TNT1 A 0 A_GiveInventory("EXEnemyToggled",1)
stop
}
}
As a closing note, just make sure to design your enemies fairly so that they don't feel overbearing to deal with as a player. Bosses are where players are challenged in combat, so there's no need to create levels filled with crazy enemies out to take everyone's lives.

How do I develop new bosses?
(click to show/hide)
Quote
Creating bosses is very similar to creating enemies, as in, it's just a matter of keeping to the standardization already set by the other bosses. You'll want to have your boss inherit off of BasicBoss and call its Spawn state and Intro states in a very similar way as to the other bosses do currently. This will ensure that the boss doesn't skip any important steps of the introduction sequence.

Failure to follow that can lead to your boss not having proper pain feedback when hit, or not receiving the proper item to signify that their super is available for usage. You'd find yourself unable to "BossSuperAvailable50%" or "BossSuperAvailable25%".

As with the enemies, any instance of damage the boss does should be followed by "*ACS_NamedExecuteWithResult("sp_cbmHP")", again, to ensure that their damage properly scales when mods such as CBM are in play.

For an example of how a boss should look in this format, reference Needleman's boss,
(click to show/hide)
Quote
actor NeedlemanBoss : BasicBoss
{
Obituary "%o was pricked by \chNeedle Man\c-."

speed 0
States
{
Intro:
NEED K 0
NEED K 0 A_TakeInventory("BossIntroFlag", 1)
NEED K 0 A_ChangeFlag("CANTSEEK", true)
NEED K 0 A_ChangeFlag("INVULNERABLE", true)
NEED K 1 A_JumpIf(floorz-z==0,"Intro2")
wait
Intro2:
NEED A 5
NEED I 5
wait

Spawn:
NEED K 0
NEED K 0 A_ChangeFlag("CANTSEEK", false)
NEED K 0 A_ChangeFlag("INVULNERABLE", false)
NEED K 0 A_JumpIfInventory("HealthScaled",1,"Spawn2")
NEED K 0 ACS_NamedExecuteAlways("EA_BossManage", 0)
NEED K 0 A_JumpIfInventory("BossIntroFlag", 1, "Intro")
Spawn2:
NEED K 0 A_ClearTarget
NEED A 0 A_ChangeFlag("INVULNERABLE",0)
NEED A 5 A_LookEx(LOF_NOSOUNDCHECK,0,0,0,360,"Found")
Goto Spawn2+2
Found:
NEED A 20
Goto See
See:
NEED A 10 A_FaceTarget
NEED K 15 A_ChangeVelocity(0.0,0.0,19.0,CVF_REPLACE|CVF_RELATIVE)
Goto Attack1
SuperChance:
NEED A 0 A_Jump(200,"Super")
Goto See

Attack1:
NEED K 1
CUTM J 0 A_JumpIf(floorz-z==0,"Land")
NEED K 1
NEED A 0 A_Jump(80,"Missile")
NEED K 1
loop
Missile:
NEED K 1
NEED A 0 A_ChangeVelocity(0.0,0.0,0.0,CVF_REPLACE|CVF_RELATIVE)
NEED A 0 A_ChangeFlag("NOGRAVITY",1)
NEED K 1 A_FaceTarget
NEED K 0 A_PlaySoundEx("enemy/needlemanfire","Voice")
NEED J 4 A_CustomMissile("NeedlemanNeedle",40,-28,random(-2,2))
NEED K 4 A_FaceTarget
NEED K 0 A_PlaySoundEx("enemy/needlemanfire","Voice")
NEED L 4 A_CustomMissile("NeedlemanNeedle",40,28,random(-2,2))
NEED K 4 A_FaceTarget
NEED K 12 A_ChangeFlag("NOGRAVITY",0)
Goto Attack1

Land:
NEED A 1
NEED A 3 A_ChangeVelocity(0.0,0.0,0.0,CVF_REPLACE|CVF_RELATIVE)
NEED A 1
NEED AAAA 2 A_LookEx(LOF_NOSOUNDCHECK,0,190,0,360,"Stab")
Goto Leap
Land2:
NEED A 1
NEED A 3 A_ChangeVelocity(0.0,0.0,0.0,CVF_REPLACE|CVF_RELATIVE)
NEED A 1
NEED AAAA 2 A_LookEx(LOF_NOSOUNDCHECK,0,190,0,360,"Stab2")
NEED A 0 A_JumpIfInventory("BossSuperAvailable50%",1,"SuperChance")
Goto Spawn2
Stab:
NEED P 5 A_FaceTarget
NEED P 0 A_PlaySoundEx("weapon/slashclaw","Voice")
NEED O 5 A_CustomBulletAttack(0,0,1,15*ACS_NamedExecuteWithResult("sp_cbmHP"),"NoPuff",250)
NEED P 5 A_FaceTarget
NEED A 15
Goto Leap
Stab2:
NEED P 5 A_FaceTarget
NEED P 0 A_PlaySoundEx("weapon/slashclaw","Voice")
NEED O 5 A_CustomBulletAttack(0,0,1,15*ACS_NamedExecuteWithResult("sp_cbmHP"),"NoPuff",250)
NEED P 5 A_FaceTarget
NEED A 15
Goto See

Leap:
NEED K 1 A_FaceTarget
NEED A 1 //A_SetAngle(angle + random(-32,32))
NEED A 0 A_ChangeVelocity(17.0,0.0,15.0,CVF_REPLACE|CVF_RELATIVE)
NEED K 8
Goto Leaping
Melee:
NEED K 5 A_SpawnItemEx("NeedlemanMelee")//A_CustomMeleeAttack(20)
Goto Leaping

Leaping:
NEED K 1 A_JumpIf(floorz-z==0,"Land2")
loop
Leaping2:
NEED K 1 A_JumpIf(floorz-z==0,"Spawn")
loop

Super:
NEED A 0 A_PlaySoundEx("enemy/bosssuper","Voice",0,1)
NEED A 0 A_ChangeFlag("INVULNERABLE",1)
NEED G 0 A_FaceTarget
NEED A 4 Thing_SetTranslation(0,62)
NEED A 4 Thing_SetTranslation(0,0)
NEED A 4 Thing_SetTranslation(0,62)
NEED A 4 Thing_SetTranslation(0,0)
NEED A 0 A_FaceTarget
NEED K 10 A_ChangeVelocity(0.0,0.0,19.0,CVF_REPLACE|CVF_RELATIVE)
NEED K 0 A_ChangeFlag("NOGRAVITY",1)
NEED M 10 A_ChangeVelocity(0.0,0.0,0.0,CVF_REPLACE|CVF_RELATIVE)
Goto Spin
Spin:
NEED Q 0 A_JumpIfInventory("CutterFlag",30,"Finish")
NEED Q 0 A_PlaySoundEx("enemy/needlemanfire","Auto")
NEED QQ 0 A_SpawnItemEx("NeedlemanNeedle2",0,0,32,14,0,random(-3,-6),random(0,360))
NEED Q 1
NEED Q 0 //A_PlaySoundEx("enemy/needlemanfire","Voice")
NEED QQ 0 A_SpawnItemEx("NeedlemanNeedle2",0,0,32,14,0,random(-3,-6),random(0,360))
NEED Q 1
NEED R 0 //A_PlaySoundEx("enemy/needlemanfire","Voice"
NEED QR 0 A_SpawnItemEx("NeedlemanNeedle2",0,0,32,14,0,random(-3,-6),random(0,360))
NEED R 1
NEED R 0 //A_PlaySoundEx("enemy/needlemanfire","Voice")
NEED QR 0 A_SpawnItemEx("NeedlemanNeedle2",0,0,32,14,0,random(-3,-6),random(0,360))
NEED R 1
NEED Q 0 A_GiveInventory("CutterFlag",1)
loop
Finish:
NEED M 16 A_ChangeVelocity(0.0,0.0,0.0,CVF_REPLACE|CVF_RELATIVE)
NEED K 0 A_ChangeFlag("NOGRAVITY",0)
NEED M 0 A_TakeInventory("CutterFlag",999)
NEED M 0 A_ChangeFlag("INVULNERABLE",0)
Goto Leaping2
}
}

actor NoPuff
{
-SOLID
+NOINTERACTION
States
{
Spawn:
TNT1 A 0
stop
}
}

actor NeedlemanNeedle
{
PROJECTILE
+RIPPER
damage (8*ACS_NamedExecuteWithResult("sp_cbmHP"))
scale 2.5
translation "13:246=4:4"
damagetype "Enemy"
Height 8
Radius 8
Speed 42
States
{
Spawn:
NHAR F 2
loop
}
}

actor NeedlemanMelee
{
+MISSILE
damage (0)
scale 2.5
damagetype "Enemy"
Height 8
Radius 8
renderstyle none
States
{
Spawn:
NHAR A 2
NHAR A 2 A_Explode(130*ACS_NamedExecuteWithResult("sp_cbmHP"),300,0)
stop
}
}

actor NeedlemanNeedle2 : NeedlemanNeedle
{
damage(6*ACS_NamedExecuteWithResult("sp_cbmHP"))
}

The next step in developing a boss would be to create a custom arena for it, it's important that this arena be a unique map from all other ones or at least have a different name, otherwise it'll overlap with other boss checks. To create this arena, just create a simple space for you to fight the boss in that has an SP Player 1 Start and a map spot with a tag of 1. The map spot is where the boss will always be spawned, so it's important to make sure that it exists and specifically has a tag of 1. You should also make sure that each sector that a player can land on within the arena has an "Actor hits floor" activator that calls the named script, "EA_BossActivate". Make sure that you don't leave any space when entering that script name or else it'll fail to be recognized. This is necessary to make sure that the boss is properly started once players land into the arena.
(click to show/hide)
Quote

The final prerequisite of implementing your boss is to create a server variable in CVARINFO that can log whether or not your boss has been defeated. This is important so that players can properly gain the boss's weapon upon his death. It should look as follows,
Quote
server noarchive bool ea_needleman = false;
Once those three aspects are in place, you can start the ACS definition needed to properly implement the boss. As like the other import files, you'll wanna start by dragging EA_BOSS.ACS into your project, but don't compile it. Then you'll want to create a new file that looks as such,
Quote
#library "sp_imprt"
#include "zcommon.acs"

#import "ea_boss.acs"

Script "sp_imports" OPEN
{
Delay(5);
defineBoss("CUTBOSS","ea_cutman","RollingCutterWep","RollingCutterWepC","CutmanBoss","RollingCutterWep","TripleCutterWep","CutterArmWep","GroundCutterWep","DuoCutterWep","GargantuanCutterWep","CutterTwinsWep","CondorSlicerWep","RollingCutterWep");
defineBoss("HEABOSS","ea_heatman","AtomicFireWep","AtomicFireWepC","HeatmanBoss","AtomicFireWep","AtomicFlamesWep","AtomicDashWep","AtomicRadianceWep","AtomicExcursionWep","AtomicWaveWep","AtomicOverheatWep","AtomicChainWep","AtomicFireWep");
defineBoss("NEEBOSS","ea_needleman","NeedleCannonWep","NeedleCannonWepC","NeedlemanBoss","NeedleCannonWep","NeedleBombWep","NeedleSprayerWep","PunctureNeedleWep","NeedleHammerWep","NeedleTwisterWep","NeedleRingWep","RevolverNeedleWep","NeedleCannonWep");
defineBoss("TOABOSS","ea_toadman","RainFlushWep","RainFlushWepC","ToadmanBoss","RainFlushWep","FlushGrenadeWep","RainTorrentWep","RainShowerWep","JusticeRainWep","FloodFlushWep","FlushRestoreWep","RiotFlushWep","RainFlushWep");
}
You'll notice that each call of that function has a lot of parameters, and that's to support the Megaman Singleplayer Classes which need to know which copywep each class should get. As a quick cheat sheet for what each parameter means, refer to this list.
Quote
// 0 - Map code that your boss is fought on (Ex. CUTBOSS)
// 1 - CVAR to toggle and check for your boss being defeated (Ex. ea_cutman)
// 2 - Vanilla weapon name according to the engine (Ex. RollingCutterWep)
// 3 - CBM weapon name according to the engine (Ex. RollingCutterWepC)
// 4 - Boss actor to be spawned according to the engine (Ex. CutmanBoss)
// 5 - Megaman weapon name according to the engine (Ex. RollingCutterWep)
// 6 - Protoman weapon name according to the engine (Ex. TripleCutterWep)
// 7 - Bass weapon name according to the engine (Ex. CutterArmWep)
// 8 - Roll weapon name according to the engine (Ex. GroundCutterWep)
// 9 - Duo weapon name according to the engine (Ex. DuoCutterWep)
// 10 - DocRobot weapon name according to the engine (Ex. GargantuanCutterWep)
// 11 - Darkman weapon name according to the engine (Ex. CutterTwinsWep)
// 12 - Fakeman weapon name according to the engine (Ex. CondorSlicerWep)
// 13 - BBAMegaman weapon name according to the engine (Ex. TrollingCutterWep)
If you know that a weapon doesn't exist for your boss for a certain class, then it is best to resort to a weapon that can be found in vanilla until it's implemented. Make sure to give a shoutout to Blews#9696 so he can know that he's got new weapons to make for the Megaman Singleplayer classes.

That's the bulk of what's needed for the implementation of a boss, so have fun creating new capstone challenges for players!

Cossack Crusaders?
I figured a quick Mission Mode inspired project would be the perfect thing to get myself and some other people around the community inspired for development again. Progress is going forward with resolve, but now I'm sure everyone will have this gameplay style in the front of their mind again.

Download Here!

For any inquiries or feedback, you can contact me on Discord at Trillster#2887

7

Projects & Creative / Modular Weapons - Concluded Tech Demo

« on: November 16, 2020, 02:32:59 AM »

(click to show/hide)

Modular Weapons - A Successful Test

Modular Weapons was a tech demo for the systems now implemented as part of Mega Man 8-Bit Deathmatch V6B. It showed that there was interest and feasibility to a setup that promoted compatibility between mods and it also helped us gauge what modders might be interested in if a system like this would be put into place, such as weapons that gain two types of ammo, means to do custom styled bars, and even further expanded systems to add and randomize new assist items.

As a result, however, this thread is now no longer needed, because the packs built for Modular Weapons are out of date and will be deprecated in favor of updating those mods for Version 6B of MM8BDM. Its legacy will live on, however, as you can now randomize all sorts of pickups in base Mega Man 8-Bit Deathmatch, so be sure to check out the new Version 6B wiki along with its documentation and server settings pages. Make sure to check the relevant threads later for weapon packs that'll be updated for Version 6B!

Visit the Wiki!

(click to show/hide)

So weapon packs are pretty cool right? I'm sure we've all got some fond memories of playing with the RNC expansion or Ukiweps. What's not cool is how the upkeep on them kinda sucks. Every MM8BDM update breaks them, requiring rebuilding of some fundamental parts of the weapon pack to fix. Not only that, but trying to load other weapon packs with each other is a surefire way to break them, unless specifically designed for. While it was workable in the past, it's not ideal, because it leads to patch file after patch file. Inspired by Jax's old Expand8BDM methods, Modular Weapons fixes that. It allows modders to design their weapon packs in a way that not only allows them to be MM8BDM update-proof, but also so that weapon packs can be hosted together, perfectly functional.

Randomizer Mode

Weapons loading together doesn't do much good without a method of getting them out into maps and into the hands of players, so that's what this part of the mod is for. Randomizer uses the modular weapon definition method to be able to replace every weapon and buster upgrade pickup with another weapon of its same type. So if you load Rockman No Constancy weapons with Randomizer, you can expect to see some Wind Slicer in the place of Air Shooter and other close weapons. Same with Circuit Breaker and rapid weapons. Load both of the wads together in any order, and you get chances for both of those to happen at once. This mode even adds in whatever extra weapons are loaded into the respective Last Man Standing pools, so you can expect to see some custom weapons in your loadout.

Modder Notes

This section won't apply to everyone and it's gonna be LENGTHY, so have a spoiler.

(click to show/hide)

Quote

Modular Weapons works with an import method, meaning for each type of definition you might need to give a weapon or item, you must have the source file from the Randomizer file for that respective definition in your weapon pack. However, you DON'T need to compile this file, and you SHOULD NOT compile it, only the files exclusive to your mod.

For example, to define a weapon's ammo and allow it to be valid for Randomizer and LMS modes, you must have the 8bdmamo.acs source file in your pack, alongside a new script file that looks like this,

Quote from: TESTAMMO.ACS
#library "testammo"
#include "zcommon.acs"

#import "8bdmamo.acs"

// 0 - Weapon Name according to the Engine (Ex. RollingCutterWep)
// 1 - Weapon Ammo according to the Engine (Ex. RollingCutterAmmo)
// 2 - Weapon Name according to the Player (Ex. Rolling Cutter)
// 3 - Ammo gain multiplier (0.0 - 1.0)
// 4 - Can be given by Eddie? (YES/NO)
// 5 - Can be Stolen by Reggae? (YES/NO) [NO LONGER USED]
// 6 - LMS Slot

Script "test_ammo" OPEN
{
Delay(1);

// Defines a weapon valid for both Randomizer and LMS, in SLOT_RANGED
defineWeapon("AwesomeBeamWep","AwesomeBeamAmmo","Awesome Beam", 1.0, "YES", "YES", "SLOT_RANGED");

// Defines a weapon valid for Randomizer but not LMS because it is SLOT_NONE
defineWeapon("AwesomeBreakerWep","AwesomeBreakerAmmo","Awesome Breaker", 1.0, "YES", "YES", "SLOT_NONE");

// Defines a weapon that's not valid for Randomizer or LMS, because it has NO for Eddie and SLOT_NONE, however it still is defined so it can pick up ammo!
defineWeapon("DawnBreakerWep","DawnBreakerAmmo","Dawn Breaker", 1.0, "NO", "NO", "SLOT_NONE");

// Defines a weapon that's exclusive to Eddie, because it has YES for him, and a slot that is not checked for by Randomizer or LMS
defineWeapon("EddieSpecialWep","EddieSpecialAmmo","Eddie Special", 1.0, "YES", "YES", "SLOT_EDDIE");
}

To define a new buster upgrade, you must have the 8bdmbus.acs source file in your pack, alongside a new script file that looks like this,

Quote from: TESTBUST.acs
#library "testbust"
#include "zcommon.acs"

#import "8bdmbus.acs"

// 0 - Buster Upgrade Pickup according to the Engine. Used for Randomizer spawns (Ex. ProtoUpgrade)
// 1 - Buster Upgrade Weapon according to the Engine. Used when another buster upgrade is used to ensure it is taken properly. (Ex. ProtoBuster)

Script "test_busters" OPEN
{
Delay(1);

// Defines a new buster upgrade with pickup name AwesomeBusterUpgrade and weapon name AwesomeBuster
defineBusterUpgrade("AwesomeBusterUpgrade","AwesomeBuster");
}

Make sure that your buster upgrade's code looks something like this so that it'll properly work with other buster upgrades in play.

Quote from: AwesomeBuster.txt
actor AwesomeBusterUpgrade : BaseMM8BDMUseItem
{
Inventory.RespawnTics 350
inventory.amount 1
inventory.maxamount 1
inventory.pickupmessage "$PU_AWESOMEBUSTER"
Tag "$TAG_AWESOMEBUSTERUPGRADE"
inventory.icon "RNCWP9"
Inventory.PickupSound "item/1up"
scale 2.0
+COUNTITEM
+INVBAR
states
{
SpawnLoop:
WEAP X 1
loop
Use:
TRBB I 0 A_PlaySoundEx("item/refill","Voice")
TRBB I 0 A_GiveInventory("BusterGiven",1)
TRBB I 0 A_GiveInventory("AwesomeBuster",1)
TRBB I 0 A_SelectWeapon("AwesomeBuster")
stop
}
}

Actor AwesomeBuster : MegaBuster
{
Tag "$TAG_AWESOMEBUSTER"
Obituary "$OB_AWESOMEBUSTER"
Inventory.Pickupmessage "$PU_AWESOMEBUSTER"
States
{
Ready:
NCH1 A 0 A_JumpIfInventory("BusterGiven",1,"TakeBusters")
Goto Ready2
TakeBusters:
NCH1 A 0 A_GiveInventory("TakeBuster", 1)
Goto Ready2
Ready2:
NCH1 A 0 ACS_ExecuteAlways(998,0,COL_AWESOMEBUSTER)
NCH1 A 1 A_WeaponReady
Goto Ready2+1
...

To define a new bar that should be shown, you must have the 8bdmhud.acs source file in your pack, alongside a new script file that looks like this,

Quote from: TESTHUD.acs
#library "testhudd"
#include "zcommon.acs"

#import "8bdmhud.acs"

// defineWeaponHud()
// 0 - Weapon Name according to the Engine (Ex. CircuitBreakerWep)
// 1 - Ammo Name according to the Engine (Ex. CircuitBreakerAmmo)
// 2 - Max amount of ammo (Ex. 28)
// 3 - Item to check for to show a flashing bar according to the Engine (Ex. WeaponCharge)
// 4 - Threshold of item needed to show the flashing bar (Ex. 40)
// 5 - Item to check for to show a darkened bar according to the Engine (Ex. SkullBarrierCooldown)
// 6 - Threshold of item needed to show the darkened bar (Ex. 1)
// 7 - Item to check for to show an overlaid bar (Ex. OilSliderFlag)
// 8 - Max amount of that item (Ex. 30)
// 9 - Cyan color of secondary bar (Ex. 4)
// 10 - Blue color of secondary bar (Ex. 128)

// defineDoubleWeaponHud()
// 0 - defineWeaponHud() call including all of its arguments (Ex. defineWeaponHUD("DualAssaultRifleWep", "AssaultRifleAmmo",200,"",0,"",0,"",0,4,128))
// 1 - Secondary Ammo Name according to the Engine (Ex. CircuitBreakerAmmo)
// 2 - Max amount of secondary ammo (Ex. 28)
// 3 - Secondary Item to check for to show a flashing bar according to the Engine (Ex. WeaponCharge)
// 4 - Threshold of secondary item needed to show the flashing bar (Ex. 40)
// 5 - Secondary Item to check for to show a darkened bar according to the Engine (Ex. SkullBarrierCooldown)
// 6 - Threshold of secondary item needed to show the darkened bar (Ex. 1)
// 7 - Secondary Item to check for to show an overlaid bar (Ex. OilSliderFlag)
// 8 - Max amount of that secondary item (Ex. 30)
// 9 - Cyan color of secondary bar (Ex. 4)
// 10 - Blue color of secondary bar (Ex. 128)

Script "test_huds" OPEN CLIENTSIDE
{
Delay(1);

// Defines a bar colored with translation (192,197) for Skull Barrier that darkens the bar whenever the user has 1 SkullBarrierCooldown
defineWeaponHUD("SkullBarrierWep", "SkullBarrierAmmo",28,"",0,"SkullBarrierCooldown",1,"",0,192,197);

// Defines a bar colored with translation (7,227) for Crypt Cloak that flashes whenever the user has 1 CloakedCheck
defineWeaponHUD("CryptCloakWep", "CryptCloakAmmo",108,"CloakedCheck",1,"",0,"",0,7,227);

// Defines a bar colored with translation (4,198) for Charade Clone that overlays another bar when the user has up to 125 CharadeCloneCharge
defineWeaponHUD("CharadeCloneWep", "CharadeCloneAmmo",28,"",0,"",0,"CharadeCloneCharge",125,4,198);

// Defines a double bar setup for DualAssaultRifleWep that colors the first bar with translation (4, 128) and the second bar with (4, 222)
// The first bar is drawn using AssaultRifleAmmo up to 200, and the second bar is drawn using GrenadeAmmo up to 16
defineDoubleWeaponHUD(defineWeaponHUD("DualAssaultRifleWep", "AssaultRifleAmmo",200,"",0,"",0,"",0,4,128),"GrenadeAmmo",16,"",0,"",0,"",0,4,222);
}

For some weapons or statuses, you might want to show a bar overlaid onto the HP bar. To do this, you'll need 8bdmhlth.acs in your file alongside a new script file such as this,

Quote from: TESTHLTH.acs
#library "testhlth"
#include "zcommon.acs"

#import "8bdmhlth.acs"

// 0 - Inventory Name according to the Engine (Ex: PlantWeakener)
// 1 - Number of defined slot to use. Max of 50, min of 1. Be careful on the slot you choose, as you can override other mods! (Ex: 32)
// 2 - Max amount of item. If you enter 0 in this field, it will draw your overlay as if the user's HP is the max amount of the item.
// Entering less than 0 will give an offset max relative to the user's HP. (Ex. 1)

Script "test_health" OPEN CLIENTSIDE
{
Delay(1);

// This definition defines a slot for SkullShieldCheck, that will draw bar 41 up to 105 SkullShieldCheck.
defineHealthHUD("SkullShieldCheck", 41, 105);

// This definition defines a slot for VirusTime, that will draw bar 42 based off of how much HP the user currently has.
defineHealthHUD("VirusTime", 42, 0);

// This definition defines a slot for PlantWeakener, that will draw bar 43 based off of how much HP the user currently has, plus 1.
defineHealthHUD("PlantWeakener", 43, -1);
}

Now that you've selected a slot for your HP overlays to use, go into TEXTURES to create the bars for them. You can also just do this by including graphics in your file in the form of sprites, but this saves some extra file size. Vertical bars use the naming scheme BRHLTXXX whereas horizontal bars use VRHLTXXX. Again, make sure that the slot you've chosen isn't going to encroach on someone else's bars or work!

Quote from: TEXTURES.BARS
// These three definitions define the bars for slot 41, 42, and 43 as defined in ACS just before.
texture BRHLT041, 8, 56{patch BARENERG, 0, 0 {translation "192:192=192:192", "198:198=197:197"}} //Skull Shield Check
texture BRHLT042, 8, 56{patch BARENERG, 0, 0 {translation "192:192=4:4", "198:198=104:104"}} //Virus Time
texture BRHLT043, 8, 56{patch BARENERG, 0, 0 {translation "192:192=4:4", "198:198=104:104"}} //Plant Weakener

// These three are just to make sure bars exist for people using horizontal bars
texture VRHLT041, 56, 8{patch BRHLT041, 0, 0 {rotate 90}} //Skull Shield Check
texture VRHLT042, 56, 8{patch BRHLT042, 0, 0 {rotate 90}} //Virus Time
texture VRHLT043, 56, 8{patch BRHLT043, 0, 0 {rotate 90}} //Plant Weakener

Pain states are handled in a similar way, there's 50 defined slots for modders to make use via replacing. So if you want to add pain states, think of the slot from 1-50 that you'll want to claim for your mod. Once again, make sure to scout around for what other mods are using so that you don't accidentally break their work. When you find the slot you want, go into "actors/player/mod" in the Randomizer pk3, and copy the respective MegamanPain file. Include that MegamanPain file in your own weapon pack in that same folder directory of "actors/player/mod" You won't need to include this file using DECORATE because it will just be replacing the file already included in Randomizer. It'll end up looking something like this,

Quote from: MegamanPain41.txt
actor MegamanPain41 : MegamanPain40 //InspiretroidMega
{
States
{
Pain.AnnihilatorBeam:
PLY1 H 0
goto Pain+1
Pain.LightBeam:
PLY1 H 0 A_GiveInventory("LightBeamProtect", 1)
Goto Pain
Pain.DarkBeam:
PLY1 H 0 A_ScaleVelocity(0.9)
goto Pain+1
}
}

Last but not least, you can define the translations that you want your weapons to use in its own separate file that'll look something like this.

Quote from: TESTTRNS.acs
#library "testtrns"
#include "zcommon.acs"

#DEFINE SOMPMISL 3340
#DEFINE LIGHTBEAM 3341
#DEFINE DARKBEAM 3342
#DEFINE ANNIHILATORBEAM 3343

Script "test_translations" OPEN CLIENTSIDE
{
Delay(25);
CreateTranslation (SOMPMISL, 192:192=4:4, 198:198=107:107);
CreateTranslation (LIGHTBEAM, 192:192=4:4, 198:198=88:88);
CreateTranslation (DARKBEAM, 192:192=88:88, 198:198=31:31);
CreateTranslation (ANNIHILATORBEAM, 192:192=93:93, 198:198=78:78);
}

It's certainly a long process, but as long as you do it well, it means that you'll be on your way to having a weapon pack that's compatible and functional with everyone else's, and that's fun for everyone involved.

Download Here!

For any inquiries or feedback, you can contact me on Discord at Trillster#2887

8

Projects & Creative / QBox Rerolled - Randomized Pickups

« on: October 31, 2020, 11:07:56 PM »

Perfect time to start modding for deathmatch again,

(click to show/hide)

QBox Rerolled

Inspired and influenced by SickSadWorld's original QBox mode, this version aims to be a more lightweight version that's built to last for all future versions of MM8BDM. Version 6 introduced some new modding tools to make that possible, so I wanted to throw my hat into the ring to show how these new tools can be used by example. It's the same simple rules as the last go. Pickups are replaced with mystery boxes that can be broken to reveal a certain type of item inside. Only this time, now the weapons are truly randomized, so expect to see far more Black Hole Bomb in your rounds.

Screenshots

(click to show/hide)

Download QBox Rerolled v1 Here!

For any inquiries or feedback, you can contact me on Discord at Trillster#2887

9

Tutorial Collection / [RESOURCE] Trill Skin Assembler for MM8BDM

« on: October 20, 2020, 07:30:18 PM »

So I think it's pretty easy to say that going from sprite sheet to skin file can be tedious and annoying. It requires you to remember the rotational numbers while manually renaming each file. I wanted to change that, so here we are.

This resource works best if you've already got a general idea of how the skin creation process works and you may want to have SLADE 3 for adjusting the automatic offsets, so be sure to check out the original skin tutorial found here, https://cutstuff.net/forum/index.php?topic=10931.0

Trill Skin Assembler

Trill Skin Assembler is a GUI-based program to allow people to create skins for Zandronum-based projects, mainly focused for Megaman 8-Bit Deathmatch. It requires far less knowledge of how programming for skins works and allows even new users to go from just a sprite sheet into a fully functioning skin.

The program has support for many extra features of skin-making, such as 8 rotations, implementing a set of crouching sprites, implementing mugshots for addons that display the mugshot as part of the UI, and implementing multiple sounds for each category.

(click to show/hide)

Note that the installer download may be false-flagged as malware. An archive download is provided for that situation. Simply download the archive download, and extract the folder within it.

Download Here

10

Closed / [Improved(?) Animation] Top Platform Voxel

« on: October 04, 2020, 03:37:59 AM »

Super subjective thing but it's always been a bit of a bother with these voxels. The voxel itself looks nice and is a good representation of the platform, but it uses Zandronum's default spinning argument which both looks uncanny when put next to other MM8BDM texturing and animation but also doesn't actually fit the rotation speed when you turn off voxels. So instead, consider doing something such as this for its VOXELDEF,

Code: [Select]

TOPPA="TOPPA" {AngleOffset = 360}
TOPPB="TOPPA" {AngleOffset = 240}
TOPPC="TOPPA" {AngleOffset = 120}

Here's the current for comparison,

Code: [Select]

TOPPA="TOPPA" {spin = 180}
TOPPB="TOPPA" {spin = 180}
TOPPC="TOPPA" {spin = 180}

And here's a video showcasing the newer animation,

(click to show/hide)

11

Projects & Creative / Objective Combo - Automated 6 Team Mode Rotation

« on: August 18, 2020, 06:08:52 PM »

This thread's been a long time coming,

(click to show/hide)

Objective Combo

Inspired by a general interest in modes such as King of the Hill and One Flag CTF, Ehibika and I helmed this project to compile six game modes into one automatically rotating mod with a bunch of settings to customize the game experience. It brought optimizations to modes like Evil Escort and King of the Hill while reworking older game modes we've seen such as Assault the Fort into a simplified mode now called Roboenza Reactor. Other modes include a new take on Screw Scramble now called Chip Challenge and a fairer paced version of One Flag CTF called Flag Ball. If those modes don't suit your interest either, there's an enhanced TLMS under the name of Arena.

Because of the concept, our goal is to have this compatible with every class mod to date, as we wanted to be able to encourage greater variety of mode past just TLMS in the server pool. A lot of work went into being able to have a proper respawn system that doesn't break class mods as a result. The settings provided follow a similar rule of thumb, they're mostly fully customizable just to ensure that our project can fit your needs in your class mod. While the settings are designed to try and give the best experience from a quick host, it's recommended to give them a read if you're looking to a host a server with a nontraditional class mod such as Unholy. It is also heavily worth noting that due to the nature of these mods, they are only compatible with CTF maps, however this does include the Recreation CTF pack and many other ones. The server must also be hosted in the TeamGame (ACS) game mode for functionality.

Game Modes

(click to show/hide)

Server Settings

(click to show/hide)

Download Objective Combo ve3 Here!

For any inquiries or feedback, you can contact us at either the 8BDM Discord (http://cutstuff.net/forum/index.php?topic=11354.0), the 8BDM Center Discord (https://www.youtube.com/watch?v=QjRAS5z-B0E), or on Discord at Trillster#2887 and Ehibika#3634

12

Projects & Creative / Ghouls versus Humans Arcade - MM8BDM Stylized GvH

« on: May 23, 2020, 06:41:28 PM »

Halloween came a bit early this year...

(click to show/hide)

Ghouls versus Humans Arcade

Largely inspired by GvH NES and previous attempts at keeping that mod alive, I felt like there was a demand for some ghouls action. However, previous attempts also ended up feeling a bit lacking in trying to design for and with MM8BDM's maps and overarching design. GvH Arcade aims to take the ghouls design and adapt it better to MM8BDM's environment through various means to push it into being a mod that's more accessible and understandable when compared to other MM8BDM mods.

One such design choice is implementing a daybreak timer for standard TLMS that allows ghouls to keep their iconic high mobility and unrestricted design while also not giving them a win condition for stalling the match out. Similarly, humans have been redesigned to focus on more specialized concepts in the way that more traditional classes might be designed, emphasizing a sense of teamwork for them compared to the ghoul side.

Alongside this goal of accessibility, the in-game menu offers easily viewable change-log menus, class-helps for informing players on how classes work, and various user options to improve the individual's experience such as toggling jump-scares, changing class control schemes, modifying how gore looks, and a death hint system for some added info when you die to a class.

Current Classes

(click to show/hide)

Humans

Megaman - Your standard MM8BDM TLMS Megaman, though he only gets 4 weapons rather than 5, opting not for a close ranged weapon.
Arthur - Seeing a fairly good facelift from his GvH NES counterpart, Arthur now focuses on his shield and high damage lance shots, making him a good class for punishing bad approaches.
Ghostbuster - While redesigned from his older counterparts, Ghostbuster is still good at denying mobility from ghouls and making them easy targets for others to deal with.
Simon Belmont - A newly designed human, Simon has various tools for keeping ghouls away and heavily threaten their approach
Mario - Another newly designed human that specializes in applying DoT and slow debuffs that highlight ghouls and make them obvious.
Cyborg - The most mobile human with a rapid fire plasma rifle and a jetpack for hovering over some more deadly grounded ghouls.
Marine - The classic Ghoul's Forest 1 and 2 protagonist. He's packing a lethal arsenal with quick bullet projectiles, but shares Megaman's need for ammo conservation.

Ghouls

Evil Robot - A ghoul analogue to Megaman who deals bonus damage when compared to him and gains close range weapons, but does not gain ranged ones.
Sjas - Your standard harassing ghoul who makes Wily UFO sounds as he moves and threatens to scream at whoever he's close to.
Mr. Stay Puft - A newly designed tanky ghoul that regenerates flat health for each instance of damage he takes, making him better against rapid attacks than strong ones.
Creeper - The classic short threat which crawls along the ground, capable of stunning and blinding people into a deadly grab.
Jitterskull - With a tricky movement system, Jitterskull is still as unpredictable as ever, but now he has the benefit of 8-directional movement.
Boo - Another newly designed ghoul that incites paranoia by summoning decoys and giving humans a paranoia that mimics other ghoul sounds.
Choke - The ghoul that started it all. Sporting the quickest speed of all ghouls, he's capable of continuous chomping and charging up for a highly lethal blood ball to flush out camps.

Screenshots

(click to show/hide)

Credits

(click to show/hide)

Download GvH Arcade v3a Here!

For any inquiries or feedback, you can contact me at the 8BDM Discord (http://cutstuff.net/forum/index.php?topic=11354.0).

13

Projects & Creative / Minecraft Classic - Nostalgia in 8BDM (v5)

« on: May 06, 2019, 04:57:43 AM »

(click to show/hide)

Minecraft Classic - Nostalgia in 8BDM

Made with the help of Ehibika and Jax with their grid snapping script and inspired by Geekie's Minecraft map, Minecraft Classic is now playable in 8BDM. Now you too can confuse Youtube's automatic game-detection! With 85 blocks at your disposal, it's possible to create whatever you desire on whatever map you'd like. OpenGL with models enabled and having buckshot enabled is recommended for the best, most polished experience.

Screenshots

(click to show/hide)

Download Here!
Version 1 Download
Version 2 Download
Version 3 Download
Version 4 Download

Changelogs

(click to show/hide)

14

Projects & Creative / Maestroid Prime Hunters - A Metroid Based Overhaul (Update! v1->v2)

« on: May 19, 2018, 10:30:25 PM »

(click to show/hide)

Maestroid Prime Hunters - A Metroid Based Overhaul

A joint project between Max, Jax, and myself, this mod aims to bring the class-based experience of Metroid Prime Hunters into 8BDM. With this, Maestroid Prime Hunters sees the return of Metroid Prime Hunter's 6 main weapons and many game mechanics such as jumping after walking off of ledges, rocket jumping, and affinity bonuses. In addition, the mod includes a reworked LMS pickup system which can be toggled on or off with the use of the "MPH_PrimeLMSStyle" server variable.

Classes

(click to show/hide)

Screenshots

(click to show/hide)

Changelog

(click to show/hide)

Download Here!
Mirror

Credits

(click to show/hide)

15

Skins & Bots etc / Trill's Voxel Props (v2)

« on: May 26, 2017, 08:36:16 PM »

Voxels count as skins right?

Trill's Voxel Props

So voxels are finally usable in Zandronum thanks to the recent 3.0 update. They're like a mix between models and sprites, but they have the benefit of being rendered in both Software and OpenGL. Along with this, much like models, they can loaded in the "skins" folder and can be used to replace sprites. Currently Core 8BDM uses these models for only platforms, so I decided to create voxels for smaller props that you can see outside of the fighting arena.

Screenshots

(click to show/hide)