Jimlad's wire addons

[Syranide]

Nice!

I've commited it, but not the applyForce-thing, yes I see your point, but the problem is that there are 4 of the functions, with the possibility of adding another 4. I don't see the point of doubling the amount of functions simply to shave off "vec()".

[Jimlad]

I've commited it, but not the applyForce-thing,

Yeah, I figured the redundancy would be off-putting, but I only did it for that one command since it's so useful for testing. It's not like it'll be hard to live without it though, it's not an issue for full-blown code where you're defining vectors anyway... it's just nice when you want to quickly write like a hover expression or something.

ZeikJT: yay, It works! It took me a second to figure out why it wasn't working at first though, it's those spelling errors I told you about!

Anyway, I've updated my first post with the new emarker code. It works a bit more cleanly now, thanks for that. I think I'll reformat my first two posts, so that the first post is only things that haven't been commited yet, and the second one is for archival. Makes it easier to check if anything new has been released.

[ZeikJT]

ZeikJT: yay, It works! It took me a second to figure out why it wasn't working at first though, it's those spelling errors I told you about!

Damn me and my horrible spelling! I thought I had gone through and fixed em all... at least you got it working. I see they've committed the version with the think function at least. I don't know if there will be reason to commit my gamemode hook version.
Does it work well? It doesn't have any reason to fail but you never know.

[Jimlad]

Yeah, it works better if anything, since I had that delay in the Think function. Now it updates the overlay immediately... probably won't make much difference, but it definitely makes for "better" code.

Thinking about it, would this approach be a good way to "fix" the applyForce functions? Create a table of entities that have the applyForce function assigned to them, and a table of force vectors, and apply the force each tick. Then the E2 functions would relate to changing the tables rather than applying force directly. Should be relatively straightforward, right?

[ZeikJT]

Haha, awesome! I might commit it myself eventually.
Good luck working on those other additions

[Syranide]

But please remove the markerlib, it's kind of pointless, especially since it doesn't have any kind of purpose.

[ZeikJT]

But please remove the markerlib, it's kind of pointless, especially since it doesn't have any kind of purpose.

What do you mean? In the past whenever I've tried adding a gamemode hook to an entity it has failed. It needs a library in the autorun to register the hook correctly... I hope I'm wrong but some of my SENTs used to fail because of this, maybe I was doing it wrong back then.
I wish I could test it... it could work. I'll rewrite it and see if anyone can get it to work.

I could also just merge the markerlib and the textlib if the above doesn't work.

[Jimlad]

Yeah, I was also confused, but that's probably because I assumed you made the markerlib file therefore it was necessary. As you say, it could always be merged. If you do a rewrite I'll give it a go.

[Syranide]

What do you mean? In the past whenever I've tried adding a gamemode hook to an entity it has failed. It needs a library in the autorun to register the hook correctly... I hope I'm wrong but some of my SENTs used to fail because of this, maybe I was doing it wrong back then.
I wish I could test it... it could work. I'll rewrite it and see if anyone can get it to work.

I could also just merge the markerlib and the textlib if the above doesn't work.

Anything that is defined with-in the entity/tool is also run.
The only difference is that what ever is in autorun doesn't have any "binding", it just exists.

Meaning, the point of stuff in autorun is for libraries or stuff that a lot of entities/tools intend to share or use. It's no point in defining something in there for a single tool, then it's better to just put it in the tool or in the entity of the tool.

[Jimlad]

ok, thanks for explaining Syranide. I've updated it and merged the code into the tool, so no more markerlib. It looks like it's working fine with the merge; linking, removing, and duplication remain unchanged. Good think you mentioned it - looks like tomb just updated the laser pointer with the same thing!