<aside> 📦 ASSTLIB.acs

</aside>

<aside> ⚡ void DrawBasicBarAndNumber(str barPiece, str barBack, str barPieceH, str barBackH, int x, int y, int id1, int id2, int id3, int barLength, bool drawnum, int number)

</aside>

Usage

This function draws a bar and a number at a given X and Y coordinate of the screen.

Parameters

• barPiece: String - The name of the graphic to draw for a piece of the bar in vertical HUD style (Ex. "ASTBARPR").
• barBack: String - The name of the graphic to draw for the bar backing in vertical HUD style (Ex. "ASSTBARE").
• barPiece: String - The name of the graphic to draw for a piece of the bar in horizontal HUD style (Ex. "ASTVARPR").
• barBack: String - The name of the graphic to draw for the bar backing in horizontal HUD style (Ex. "ASSTVARE").

<aside> 💡 Warning: A bad “gotcha” with core graphics is that they are typically flipped in their naming scheme due to legacy reasons. Any graphic with VAR typically refers to the horizontal alternative rather than the vertical as you might expect!

</aside>

• x: Fixed - The X coordinate of the screen that the bar’s respective image is drawn at.
• y: Fixed - The Y coordinate of the screen that the bar’s respective image is drawn at.

<aside> 💡 **Note: Because this function is implemented using HudMessage internally, the X and Y coordinates here abide by the rules of SetHudSize as that function does.

If you’re using [Get_AssistDisplayBar_X](<https://mm8bdm.notion.site/Get_AssistDisplayBar_X-b1024a0668234f129edaf36a126c7b81>) and [Get_AssistDisplayBar_Y](<https://mm8bdm.notion.site/Get_AssistDisplayBar_Y-031bc9a7a82f448fbb4797839a35c692>), this is not much of a concern to you, because they already give coordinates assuming that SetHudSize(320, 200, 0) has been used, but it is good to know for specifying your own coordinates!**

</aside>

• id: Int - Internally this function uses HudMessage which requires an ID, so you should pass a unique HudMessage ID using [Get_And_Inc_AssistDisplayID](<https://mm8bdm.notion.site/Get_And_Inc_AssistDisplayID-00a4e858bdcd4550ab346852f18050be>). Alternatively, you can supply your own static IDs, just make sure that they are unique!
• id2: Int - The implementation of this uses three HudMessage IDs, one for the number, one for the bar pieces, and the third for the bar backing, so this function requires you to provide three IDs.
• id3: Int - The implementation of this uses three HudMessage IDs, one for the number, one for the bar pieces, and the third for the bar backing, so this function requires you to provide three IDs.
• barLength: Int - How many bar segments to draw out of 8. If you have an inventory that is measured in tics for duration, you can use an expression such as this, ((CheckActorInventory(cam,"BeatSupportCounter") * 8.0 / BEAT_SUPPORT_MAX) + 0.5) >> 16.
• drawnum: Bool - The number should only be shown if the user has it enabled, so typically this expression is put into this argument, CheckActorInventory(cam,"AssistNumberFlag")>0.
• number: Int - The actual number to show on the display if enabled. If you have an inventory that is measured in tics for duration, you can use an expression such as this, CheckActorInventory(cam,"BeatSupportCounter") / 35 + (CheckActorInventory(cam,"BeatSupportCounter") % 35 > 0).