06000208 / ttt-gravity-gun Goto Github PK

There's actually two methods for creating a custom ttt weapon regarding your lua file's name and path, with this addon currently using the first:

• lua/weapons/weapon_ttt_gravitygun/shared.lua
• gamemodes/terrortown/entities/weapons/weapon_ttt_gravitygun.lua

The latter is described in ttt's custom weapon guide while I don't remember where I learned the other.

I'm unsure if there would be any advantage to switching, if either is preferred over the other, etc.

Some of this stuff is already partially in the code, although commented out.

• Punting is the act of applying force to your prop via left click, held or not
• Pulling is pulling something towards you using right click
• Grabbing is the act of picking something up using right click
• Holding is when you have something held after grabbing using the gravity gun
• The "tongs" are the bits of metal on the front of the gravity gun

Visual

• The vibrant orange glow
• Increased glow when you attempt to grab but aren't looking at anything grabbable
• Increased glow and "tong" lights when holding
• Muzzle flash on end of the gun & sparks at punted location when punting
• Beam of orange electricity when punting
• Animated gauge when punting or grabbing (but not pulling)
• Animated tongs: Open when looking at something grabbable or while holding, other wise closed.
• Make tongs more visible in the shop icon
• Add the weapon's orange glow to the shop icon to make it slightly brighter (maybe)

Sounds

• Left click when not looking at anything puntable (unable to punt)
• Right click when not looking at anything grabbable (unable to grab)
• When you look at something grabbable (tongs open)
• When you look away from something grabbable (tongs close)
• When grabbing something (grab)
• While holding something (holding)
• When dropping something (drop)
• When punting something (punt)

SetDeploySpeed needs to be used in the initialize meta function for it to do anything

Rather than a certain amount of uses, ammo should be reflected as "energy" or "charge", where punting consumes a certain percentage and pulling/holding are gradual drains, all three determined by the weight of the prop being acted upon

Particularly:

• Limits and tolerances for what props can be picked up
• Which roles can buy it from the shop

Right click (pulling props or entities) is nonfunctional. Left click (pushing) outputs a serverside error;

Lua Error: [TTT Gravity Gun] lua/weapons/weapon_ttt_gravitygun/shared.lua:644: Tried to use a NULL entity!
1. SetParent - [C]:-1
2. Visual - lua/weapons/weapon_ttt_gravitygun/shared.lua:644
3. oldprimary - lua/weapons/weapon_ttt_gravitygun/shared.lua:453
4. unknown - addons/tttdamagelogs_3.1.0/lua/damagelogs/server/damageinfos.lua:55

Code segment in question;

    if (SERVER) then
        if !self.Muzzle then
            self.Muzzle = ents.Create("PhyscannonMuzzle")
            self.Muzzle:SetPos( self.Owner:GetShootPos() )
            self.Muzzle:Spawn()
        end

        self.Muzzle:SetParent(self.Owner) -- L644
        self.Muzzle:SetOwner(self.Owner)

        timer.Simple( 0.12, function()
            self:RemoveMuzzle()
        end )
    end

This has something to do with setting the owner of the weapon to a muzzle flash. This is probably self.Muzzle equalling the NULL entity, but its been a while so that may be me reading the error wrongly. Possible fix would be to change the !self.Muzzle to not IsValid(self.Muzzle).

Edit: switched right and left around.

As self.Weapon is the same as just self in SWEPs

• Heavy props (such as cars) should reflect their weight when held, such as a slight decrease to movement speed along with a noticable "drag"
• Ideally it would also be much harder to flick them, abusing the physics engine, but that's also a fun part of the weapon

Such as the seesaw on ttt_richland

Revisiting addon and lua development after programming in other languages, I find myself wanting real IDE features for it, and a better workflow for building addons, testing them, and releasing to the workshop/on github. I'll be using this issue to document my findings in various editors and what I think works best