Lua Errors

[phoenixf129]

ERROR: GAMEMODE:'Tick' Failed: terrortown\gamemode\player.lua:1213: attempt to call method 'GetIronsights' (a nil value)

Not very important, but thought id post it.

Now for the important one, this one makes the game bug out and stick in Preparing until i forcechange map or restart  the server:

Timer Error: terrortown/gamemode/init.lua:689: bad argument #1 to 'insert' (table expected, got nil)

If a fix is out, i'd like to be pointed in its direction ;)

~Phoenix

[Bad King Urgrain]

Are you running custom weapons? edit: According to the other thread you do. One of them is broken.

Other modifications?

[phoenixf129]

The timer error is in default TTT, i've tried upping a clean version for a week, and it still has the preparation bug..

EDIT://

Found out hte source of the IronSight bug for me, i was developing a utility, and failed ;) It was going to be a Body Proximitator ( Finds dead bodies and beeps quicker when you get closer. )

Secondly a clientside error:

terrortown/gamemode/cl_init.lua:164: attempt to call method 'SetRole' (a nil value)

:S

[Charles445]

SetRole only happens once when a player loads quicker than the gamemode.

[JoTheShmo]

If you are developing something for it, then you are bound to get many errors that we can't fix here.

[Bad King Urgrain]

The timer error is in default TTT, i've tried upping a clean version for a week, and it still has the preparation bug..

Yet no one else seems to have it.

edit: If you have a lead as to when it happens or what seems to cause it, that would help.

edit2: Something else I forgot to mention: I would only expect that timer error if some earlier code did not execute due to some other error, so perhaps there is a different error further back in the console/log.

terrortown/gamemode/cl_init.lua:164: attempt to call method 'SetRole' (a nil value)

I believe I've found the cause of this one. It only happens in a specific situation where the map switches and as your client finishes loading up the map, the server sends you something before your client is done initializing all Lua scripts. Won't have any negative effects, and should be fixed in next version.

[phoenixf129]

ERROR: GAMEMODE:'DoPlayerDeath' Failed: terrortown\gamemode\player.lua:911: attempt to call method 'DampenDrop' (a nil value)

ERROR: GAMEMODE:'DoPlayerDeath' Failed: terrortown\gamemode\scoring.lua:84: attempt to call method 'GetTraitor' (a nil value)

Possibly a few of these.

[Bad King Urgrain]

First one is due to a custom weapon not having weapon_tttbase as its base class or having other issues, much like the GetIronSights error above.

Second would involve blowing up an NPC, which I suppose is possible because some maps insist on adding those. I'll fix that one.

Neither would cause the timer error though. If those are all the errors you get, I'll put up a new update tomorrow with the fixes I have so far and we'll see how things go.

[phoenixf129]

Well, i fixed my IronSights bug and DampenDrop... Was caused by a single typo in my mp5's coding.

As for the rest, good luck with those ;)

Mind posting an invididual lua change report instread of "changes in terrortown/gamemodes" since its hard to keep my custom stuff, if i dont know was fixed / changed.

[Bad King Urgrain]

You can use a diff tool like WinMerge to easily visualise the changes made in an update.

[phoenixf129]

Useful ;)

Thanks!

Now, il keep an eye out for bugs..

Wait, got one! xD

When you buy traitor body armor, or even any of the three red ones at the top, they dont fade till you re-open the Context menu, unless you designed it like that of course..

[toco123]

Would it be correct to presume custom weapons must be rescripted to work on the ttt_base?

[Bad King Urgrain]

Depends what you mean by custom weapon. If you're asking about existing custom TTT weapons, then no, since the beginning of TTT all weapons have had to set SWEP.Base = "weapon_tttbase" in order to work without loads of errors. It's not something new.

If you mean SWEPs that were made for sandbox, they will require modification, yes.

[toco123]

I meant adding a swep that was made under a different base, which you have answered.

[phoenixf129]

Detective beacon icons ( the blue hud logo ) stay on screen after round end. Maybe this is fixable, as i'd like to keep the Beacons as an option for DET, as they are underpowered and don't really have enough other than innocents who dont even protect them ;)

[Bad King Urgrain]

With "after round end", do you mean after a new round starts?

[phoenixf129]

Yeah, the detective HUD display for beacons stays over rounds, even though the box is gone, the area where it was last still shows the icon for players.

[Bad King Urgrain]

Odd, because everything is definitely cleared out in the code. I can't really be bothered to re-enable everything just to test.