Shepard62700FR
func_tankrocket entity (HGrunt uses them during the "On A Rail" chapter).When the game/mod starts, issue the map <your fancy background map here> commandThis can be done by putting the command in a RC or CFG file.
have some kind of if ( thisIsMyMenuMap ) condition to show that new main menu (powered by VGUI or another UI framework if you use one). Then you issue commands depending on the buttons being clicked. For example: "New Game" button would issue map <your first map here>. "Load game" would load up the default load dialog.That would be client sided.
void CFuckfinger::SecondaryAttack(void)
{
void;
}void; thingy is useless (maybe you meant return;?)void CFuckfinger::Reload(void)
{
// Ammo check and actual reload code here
if (iResult)
{
m_flTimeWeaponIdle + UTIL_SharedRandomFloat(m_pPlayer->random_seed, 10, 15);
}
}m_flTimeWeaponIdle =void CFuckfinger::WeaponIdle(void)
{
// Reset empty sound, autoaim and "time to idle check" code here
if (m_iClip != 0)
{
int iAnim;
float flRand = UTIL_SharedRandomFloat(m_pPlayer->random_seed, 0, 1);
if (flRand <= 0.5)
{
iAnim = FUCKFINGER_IDLE;
m_flTimeWeaponIdle + 70.0 / 30.0;
}
else if (flRand <= 0.7)
{
iAnim = FUCKFINGER_IDLE;
m_flTimeWeaponIdle + 60.0 / 16.0;
}
else
{
iAnim = FUCKFINGER_IDLE;
m_flTimeWeaponIdle + 88.0 / 30.0;
}
SendWeaponAnim(iAnim, 1);
}
}UTIL_WeaponTimeBase() in the calculation which is the current game time. And the final problem is that you are randomly picking one of 3 possibles scenarios but all of them play the same idle animation (the idle time being the only difference). You could simplify your WeaponIdle function to something like this:
void CFuckfinger::WeaponIdle()
{
ResetEmptySound();
m_pPlayer->GetAutoaimVector(AUTOAIM_10DEGREES);
// Play idle animation only if it is time to do so and the clip/magazine isn't empty
if ( m_flTimeWeaponIdle > UTIL_WeaponTimeBase() || m_iClip <= 0 )
return;
SendWeaponAnim( FUCKFINGER_IDLE );
m_flTimeWeaponIdle = UTIL_WeaponTimeBase() + 3.0f; // Assuming your idle animation duration is 3 seconds
}map <your fancy background map here> command, that map would trigger an entity or your code would have some kind of if ( thisIsMyMenuMap ) condition to show that new main menu (powered by VGUI or another UI framework if you use one). Then you issue commands depending on the buttons being clicked. For example: "New Game" button would issue map <your first map here>. "Load game" would load up the default load dialog.There will be a SL Single-Multiplayer source then?It is not that I will start anything in a near future, but it could be interesting for people to start doing something cool with the GS code using your "mod".No, Solokiller said in a previous post when he redesigned the engine that the game source code is gonna be a "client/server/shared" architecture where client-only stuff goes into the client part, the server-only stuff goes into the server part and everything common to the client and server goes into the shared part.
btw how long do you think until someone will create a non vr version mod ? XDA "flat" version of HL:A would be "boring" as you would lose all the interactions that VR grant.
My speculation is, less than 4 months after the SDK releases, if they provide one.Right now, it is confirmed that we'll have Hammer 2 for HL:A. As for a "standard source code" à la GoldSrc/Source (even complete), nothing official yet.
Give me some info before... What game mode will be used, singleplayer with deathmatch 0 or multiplayer with deathmatch 1? Is gauss hopping allowed?Likely singleplayer, as for gauss hopping, it depends if Spirit of Half-Life 1.8 allow it in singleplayer.
I would have rushed something out in the last year or so to get it over the line.Don't make the same mistake as we did with Half-Rats: Parasomnia. Take the time you need to finish it and most importantly: have a lot of people playtest the shit out of it (different play styles, profiles...)
Should probably finish this mod, huh?Not sure if this is the truth...... or a trap for hype.
Very excited. Have an idea in my head that I've wanted to try for ages. Does it strictly have to be HL1 / Source or is something like Sven Coop applicable?The competition refers to "the" player in singular, so I'm guessing that only singleplayer games in the Valve universe are allowed.
Well, the issue there would be the difference between Source and Goldsource. I have no idea how to set up a Source mod.I can handle that.
And can we get an official word specifically on custom code, because I feel like that is sort of a different level of custom content that doesn't tend to fit with these sorts of competitions.To be fair, the code and binaries would need to be open to everyone even non-programmers.
Good quality desktop right thereIn my opinion, it may do the opposite. It may encourage people. I've never used C#, but from what I hear and see here, it seems easier than C++It is, in high programming languages (C#/Java), you don't have to deal with pointers (but you still need to worry about "null references"), memory allocations, memory leaks and more, the language does that for you. The only problems (which aren't really problems if you ask me) is you need a "Common Language Runtime" (.NET Core Runtime in the case of Sharp-Life) to run the code and it can be easily reverse engineered (yeah I know about obfuscation). C/C++ being low level programming languages are "closer to the machine", it's the opposite.
Then there's the question of doing it from scratch. If the HL SDK is ported to C#, do we replicate the changes which we made to our C++ HL SDK code over to the C# HL SDK, or something else?My guess is that you will need to start from scratch, there are already so many differences that you can't just move your C++ code over to C#. Let's take an example: to save/restore entities data, the C/C++ way is to declare and use a save/restore table. Sharp-Life through the power of C#'s annotations handles the save/restore table already for you and you just need to annotate the variables you want to be saved/restore.
// Might be wrong here
TYPEDESCRIPTION CTWHL::m_SaveData[] =
{
DECLARE_FIELD( FIELD_BOOLEAN, CTWHL, m_bStatusSent )
};
IMPLEMENT_SAVERESTORE( CTWHL, CBaseEntity );// Might be wrong here too (feel free to correct me Solokiller if I messed up)
class CTWHL
{
[Persist]
bool StatusSent;
}