Skip to content

Ghostbusters movement speed issue #196

Description

@tilderain

On start, it sets max movespeed for each of the classes, but in my experience as heavy, seems like the speed only randomly applies correctly like 1/10th of the time for some reason.

SetPropFloat(player, "m_flMaxspeed", 320.0)
}
else if (medics.find(player) != null)
{
Ware_SetPlayerMission(player, MISSION_MEDIC)
Ware_SetPlayerClass(player, TF_CLASS_MEDIC)
Ware_StripPlayer(player, false)
Ware_SetPlayerTeam(player, TF_TEAM_BLUE)
Ware_GivePlayerWeapon(player, "Medi Gun", { "ubercharge rate penalty" : 0.0 })
Ware_PassPlayer(player, false)
SetPropFloat(player, "m_flMaxspeed", 300.0)
local minidata = Ware_GetPlayerMiniData(player)
minidata.last_target <- null
minidata.vo_timer <- 0.0
}
else
{
Ware_SetPlayerMission(player, MISSION_GHOST)
Ware_SetPlayerClass(player, TF_CLASS_SPY)
Ware_StripPlayer(player, false)
Ware_SetPlayerTeam(player, TF_TEAM_BLUE)
Ware_TogglePlayerWearables(player, false)
Ware_GivePlayerWeapon(player, "Fists", { "no_attack" : 1 })
player.SetCustomModel(ghost_model)
player.SetCollisionGroup(COLLISION_GROUP_DEBRIS_TRIGGER)
Ware_AddPlayerAttribute(player, "reduced_healing_from_medics", 0.0, -1)
Ware_AddPlayerAttribute(player, "cancel falling damage", 1.0, -1)
SetPropInt(player, "m_nRenderMode", kRenderTransColor)
SetEntityColor(player, 255, 255, 255, 60)
SetPropFloat(player, "m_flMaxspeed", 280.0)
player.SetForcedTauntCam(1)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmedThis issue has been verified on a listen server, or otherwise confirmed to be TF2Ware's fault.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions