@sexpert said in Broken Scripts:
@rickk-0 you have to start it twice in the menu. idk why but the first time you click run it doesn't do anything. second times starts right up. SPX tut.
I'm an active scriptwriter. I have an update coming soon to add support for the new naming system.
New RSPeer rules are as follows:
[CHAT RULES]
General Rules (All Channels)
No flaming (includes racism, harassment, threats, insulting other members, etc.)
No spamming
No trading
No advertising
No illegal content
Keep content in relevant channels
Channel Specific rules
Casual
No excessive flaming (racism, IRL threats, etc.)
No excessive spamming (e.g. 10+ messages in 5 seconds)
No trading
No advertising
No illegal content
The channel is lightly moderated and as such rules will be enforced at Staff discretion
Penalties
If you break the above-mentioned rules the penalties are as follows:
First offence – Warning
Second offence – 24 hour mute
Third offence – 48 hour ban
Fourth+ offence – 7 day ban
Permanent ban if you persist or for especially grievous offences
These are only guidelines, the actual punishments may vary slightly at staff digression.
[PRIVATE SCRIPTING RULES]
General Rules
Private script sales are to be conducted through members with the Verified Script Seller rank
Verified Script Sellers will either be tasked with providing the script themselves or delegating the task to a Script Writer while providing code review to ensure account security and quality
Exceptions will be granted for Script Developers (not to be confused with Script Writers) and Moderators (or higher)
This system will be replaced with an official SDN based private scripting system at a later date
TL;DR for clarity: PM members with the Verified Script Seller rank on Discord for private scripts until the SDN is complete, Script Writers aren't allowed to take on commands independently
Penalties
Script Writers or regular members found to be breaking the rules will be demoted or banned at Staff discretion
@xsteven09x said in RSPeer 1.30 Changelog:
I don't know it its script based, but I keep on getting this error: "Jan 23, 2019, 9:46:08 PM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.net.SocketException) caught when processing request to {}->http://pathing.acuitybotting.com:8080: SOCKS: Connection refused"
It happens with a lot of scripts when they try to walk to a specific spot. Is it caused by my proxies? Or are the webwalking servers just down.
I'd guess that it may be a server issue assuming your proxies are fully operational (as it's failing to connect to acuity, which is the rspeer server from what I've gathered).
RSPeer face is angry now
A possible bug: both instances completely closed on me. Restarted, went to bank, and it completely closed by itself again.
Seems to be working for now.
@Erradicado said in Bot Management Panel - Alpha Access:
Is there any way to change the script that the client is running without closing the client?
Not at the moment but that could be a feature added on.
@sexpert said in Introducing Unlimted Instances Per Month:
i 2nd Slut's idea, setting it equal to the price of 50 instances.
@Warrior you have to consider what this bot does that others do not. at 75cents an instance you can EASILY make your money back, even using the free scripts on the sdn will net you your money back + profit. Rspeer gives 3 FREE instances with no time based limit, as far as i know they are the only botting platform to do that (maybe dreambot too). There is no "special feature" and it still outperforms all other public clients (example being looking glass, stealth mode, ect.). Rspeer handles extremely fast in comparison to other clients. (example being DD's jug filler) rspeer filler hits 4k an hr while Dreambot only hits 3.7k (same script, same writer). I personally enjoy the fact that the devs for Rspeer are active and efficient at posting updates and keeping the community informed. Coming from someone who has used almost all public and paid bots since 2004.
To add onto that, the only reason you'd pay for unlimited instances is likely to run 50+ bots. If you can't make back 50$ in a month with 50 bots, then you are doing something wrong.
@MadDev have you guys written the infrastructure to extend licenses in those situations? I'm especially curious if the users license for the script expires during the downtime, when extending licenses would you be reauthorizing the user for the time that the platform was experiencing issues?
