Team Spartan Cookies & Milk Forums
  • Issue Tracker
  • Donations
  • Search
  • Member List
  • Help

Register

Team Spartan Cookies & Milk Forums Feedback Suggestions and improvements v
« Previous 1 2 3 4 5 6 … 36 Next »
Strength & Refire Rate outputs for weapons
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threaded Mode
Strength & Refire Rate outputs for weapons
07-05-2021, 08:13 PM,
#1
The17thDoctor Offline
TSCM Average Enjoyer
****
Posts: 1,100
Threads: 249
Joined: Oct 2015
Strength & Refire Rate outputs for weapons
Everything's in the title, said outputs could be useful.

I'd still like to re-push my point on the fact that reading inputs instead of needing extra outputs for everything would be really handy. 
I realize it kind of breaks Wiremod's "rules" but at the same time they're not official rules per say and more mechanisms that were made by the devs this way from what I know. As long as reading inputs is reserved to entities we have toolgun permissions on, I personally don't see a problem.

The17thDoctor: Server take me to the most handsome person
srcds_linux: I cant send people to themselves...
Website Find
Reply
07-05-2021, 08:14 PM,
#2
mariofludd Offline
Novaaaaaaaaaaaaa
****
Posts: 528
Threads: 44
Joined: Dec 2013
RE: Strength & Refire Rate outputs for weapons
pLEASE let us read inputs I NEED IT SO MUCH

[Image: efN9HsZ.png]
Find
Reply
09-05-2021, 10:49 AM,
#3
Person8880 Offline
gpj.ecafllorT
*******
Posts: 2,407
Threads: 45
Joined: Sep 2013
RE: Strength & Refire Rate outputs for weapons
What's the use case for needing to know the strength/fire rate here?

You shouldn't need to read inputs as you should already be in control of them and thus know what they're set to. Inputs are supposed to be private to an entity.
Find
Reply
09-05-2021, 11:44 AM,
#4
The17thDoctor Offline
TSCM Average Enjoyer
****
Posts: 1,100
Threads: 249
Joined: Oct 2015
RE: Strength & Refire Rate outputs for weapons
The problem with not being able to read inputs is that we're not always directly "in control" of our inputs. If I was to take a starfall / E2 script that would not allow me to explicitely retrieve the Refire Rate / Strength it's automatically applying then I'd not be in measure of telling both parameters without having to just debug the entity in question. As for Refire Rate / Strength, it could allow for some scripts like Power Management scripts to be made, e.g Power Failure ETA or managing power such as it balances with energy generation. I don't really get why inputs should stay private to the entity as we can literally read them using the Debug feature. I can agree that not everyone should be able to see everyone else's inputs but if added some securities like SF special permissions to read inputs & toolgun permission checks, it could get really handy and we'd be able to determine certain things from Entities without needing extra outputs.

The17thDoctor: Server take me to the most handsome person
srcds_linux: I cant send people to themselves...
Website Find
Reply
09-05-2021, 01:20 PM,
#5
Person8880 Offline
gpj.ecafllorT
*******
Posts: 2,407
Threads: 45
Joined: Sep 2013
RE: Strength & Refire Rate outputs for weapons
For a power management chip to work it would have to be able to control the inputs, right? It's not so much about permissions as it is about the concept of reading an input from outside being at odds with how Wiremod works.

If you have something controlling inputs then it should know what those values are already. Trying to have multiple things controlling an input doesn't work, hence wire inputs only being able to be connected to one output at a time. While yes, you can have multiple wirelinks and trigger inputs through them, it still results in a clash and you ultimately still want one thing controlling them. Once you have one thing in control, you know exactly what the input values are as they've been set by it. There are also functions to get the entity and output name that an input is wired to, which you can read to know the input value (and detect changes) in the case it's wired manually and not controlled by a chip.

The debugger is, as the name suggests, a debug tool. It shows you inputs because its purpose is to inspect the wiring functionality of an entity. A chip shouldn't need debugging level access to be able to work.
Find
Reply
09-05-2021, 06:46 PM,
#6
mariofludd Offline
Novaaaaaaaaaaaaa
****
Posts: 528
Threads: 44
Joined: Dec 2013
RE: Strength & Refire Rate outputs for weapons
(09-05-2021, 01:20 PM)Person8880 Wrote: If you have something controlling inputs then it should know what those values are already.


Personally I'd love it for something like a weapons status screen, the chip doesn't do any controlling, it just displays the status of the weapons. Sure I could wire the controller to the screen, but its easier and more efficient to just be able to get the inputs (And if its a screen I've given to something else, I have no clue what the control is, and theres a possibility they don't either if its an automatic thing from a mainframe or something)

[Image: efN9HsZ.png]
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
Forum Jump:


Users browsing this thread: 1 Guest(s)
Contact UsTeam Spartan Cookies & MilkReturn to TopLite (Archive) ModeMark all forums readRSS Syndication

Powered By MyBB, © 2002-2026 MyBB Group.