Author Topic: JVS onContent events  (Read 3788 times)

you know rather than being a tard planr you could answer his loving question
http://orbs.daprogs.com/rtb/forum.returntoblockland.com/dlm/viewFile98dc.html?id=45
pretty sure this is what you need, by the way if you want to keep using jvs instead of default brick doors i would suggest switching over to support_legacy since a lot of problems jvs had are fixed with it. you can find a better version of it here

apparently op fixed the problem and i didn't read, still though planr forget off already
« Last Edit: December 11, 2017, 03:57:16 AM by torin² »

let the poor man use jvs if he wants to. I agree legacy is better tho

you know rather than being a tard planr you could answer his loving question
apparently op fixed the problem and i didn't read, still though planr forget off already
I know you just like to talk stuff every time you see me post somewhere, but don't even try to lie to my face about what I did or didn't do. I did answer the OP's question and I gave him the exact information he asked for. Aside from Crispy, I was the only other one that helped OP in the way he wanted at that time. I may not like that OP wants to use JVS but I still helped him regardless.

You call me a tard for advising him to use legacy instead of JVS, yet you're just reiterating the same thing I already said:
by the way if you want to keep using jvs instead of default brick doors i would suggest switching over to support_legacy since a lot of problems jvs had are fixed with it.
JVS has specific problems that make it a poor choice for use in door events.
Here's an example of some problems with JVS, the ones relevant that Badspot brought up before

You forget off.
« Last Edit: December 11, 2017, 03:47:47 PM by Planr »

You better care, because next time you have a problem with JVS, no one is going to care to help you (since you won't listen), and I certainly am not going to make that same mistake twice.
Alright, because you speak for literally everybody on the Blockland loving Forums. Thanks for the heads-up.

Planr nobody loving cares about your bullstuff substitute for JVS considering it doesn't actually exist. What is your malfunction?

So your entire argument is that newer things came along and therefore it is obsolete?

Newly-created Add-Ons get stuff on if they are duplicates of others' Add-Ons, perhaps with the only exception being weapons that are real-world models but in other packs. They also get stuff on if they break existing Add-Ons.

You shouldn't be using JVS. It slows down/breaks the game. Stop using it.
Slows down the game? I have a computer which can hardly run any kind of game at all and I get no noticable impact with JVS doors. So tell me why anyone who isn't using a potato shouldn't use it for this reason.

Breaks the game? Only when you're an idiot and try to use conflicting Add-Ons. Add-On management has always been this way.

So what other than your opinion do you have to present here? Why is JVS seemingly the ONLY Add-On where it's so-called prior claim comes along because someone made a version that successfully operates on a toaster?
« Last Edit: December 12, 2017, 03:55:07 PM by SWAT One »

Problems with JVS doors:

  • 16 events to open a goddamn door.
  • stuffty AIM sounds
  • Ego-wank "jvs" tab instead of being in the special/interactive tab where they belong
  • Ass-backwards-as-forget loop structure that causes the brick loading times to increase for all bricks for each jvs door that you have installed.  If you have 50 JVS doors installed, you're looking at a 10x increase in loading times.  This alone is reason to remove it from the game permanently.  I regret not CRC failing when I discovered this issue years ago. 
  • Overly complicated door blocking system that requires a taxing container radius search every time someone opens a door.  Door disabling can easily be implemented via toggleEventEnabled or setRayCastingEnabled.
  • Overly complicated ID restriction system that serves no purpose except providing yet another way for power starved pre-teens to give themselves special privileges over other users so they can have some semblance of empowerment in their otherwise impotent lives.
there are valid reasons to stop using jvs but planr has 0 argumentative skills so he comes across as a braindead paint huffer in every single one of his posts

So your entire argument is that newer things came along and therefore it is obsolete?
Wtf? That's not my argument at all, you're fabricating a total straw man. The reasons I listed for not using JVS have nothing to do with its age. Reread my post.

Newly-created Add-Ons get stuff on if they are duplicates of others' Add-Ons, perhaps with the only exception being weapons that are real-world models but in other packs.
For example?

They also get stuff on if they break existing Add-Ons.
In some cases, this is a valid reason to dislike new mods if they break pre-existing ones, but when it comes to two mods that are trying to do the same job in different ways (eg. JVS_content and legacy), of course one must pick one over the other as having both is like trying to drive a car while it's in neutral.

Slows down the game? I have a computer which can hardly run any kind of game at all and I get no noticable impact with JVS doors. So tell me why anyone who isn't using a potato shouldn't use it for this reason.
Reread the post Torin just quoted by Badspot. The JVS_Content door system increases build loading times exponentially. That's why most people have stopped using JVS Content and switched to Legacy to run their JVS doors more smoothly.

Try planting down a hundred .dts static shape doors (JVS) and see how rapidly your FPS drops when looking at them, VS 100 BLB doors. The difference is massive because .dts static shape doors cause huge performance drops. This is neither myth nor rocket science. Go and try it for yourself.
That being said, I still use static shape doors with legacy because I hate doors that don't have animations, but I also understand why Legacy is superior to JVS (one event to open a door vs 16, faster loading times, etc). I'm able to afford the FPS with staticshape doors drop more or less. Most people can't though (blame blockland's inability to multi-thread).

So what other than your opinion do you have to present here?
Advising someone that JVS_content has inherent flaws that legacy does not is not "my opinion", it's a demonstrably true statement of fact.

Why is JVS seemingly the ONLY Add-On where it's so-called prior claim comes along because someone made a version that successfully operates on a toaster?
Reread Badspot's post.

Planr nobody loving cares about your bullstuff substitute for JVS considering it doesn't actually exist. What is your malfunction?
If you don't care, then be quiet. The reason I brought it up was because this is a suggestion thread (it's posted in suggestions/requests), it's a valid idea that I've consulted with multiple modders and they've affirmed it can work, and because it would be beneficial to everyone if it was made. There is nothing "bullstuff" about it.
« Last Edit: December 12, 2017, 04:37:45 PM by Planr »

even then op can use whatever the forget he wants

I agree Torin. Nobody's saying he can't. I advised him to stop using it and he declined, so that's the end of that.

OP can use whatever he wants but I'd prefer him not using JVS if the server will be hosted online because JVS is just broken/inefficient in a ton of different ways and kills brick ghosting times for everyone.

I agree Torin. Nobody's saying he can't. I advised him to stop using it and he declined, so that's the end of that.
End? You kept going after I already told you I'm going to use JVS if I so choose. I can respect giving me reasons JVS might be outdated like Torin is doing, but once I tell you that I'd rather keep using it for the time being, that's the appropriate time to end it.
Regardless, I'm locking this thread because it's pointless to keep it going any longer.