Forums » Suggestions
Simple Convenient Ingame Method for Bot Networks
Sorta like how Steam made game piracy plummet, I think if we implement a simple, convenient, and fair way for guilds to create bot networks ingame, it'll stop all the arguing about the SCIN. Anyway, here's one idea....
((these are all just general suggestions, it's more the concept as a whole I wanted to get at))
Port: Large
Ammo Capacity: 3
Grid: 10
Weight: 2000kg
The bots it would launch would either be Fennus Observers or a new class, and the same faction as the player who launched them. Once launched, the player/guild who owns them would be given access to the bots' armor status and sensor log. These bots would be stationary, have a sensor range of 5km, have some form of limited lifespan, and have a limit of how many the player/guild could have active at a time. Station defenses would treat them the same way as mines (fired upon by capgauss but left alone by station guards), unless a Serco bot is dropped at an Itani station or vice versa, in which case the station guards would attack them. If docked at a station or capital ship, the owner of the bot can remotely pilot it into sectors he or she wishes to monitor, but there would be some form of limit to how often it can jump to prevent quick blow-throughs.
So yeah...thoughts?
((these are all just general suggestions, it's more the concept as a whole I wanted to get at))
Port: Large
Ammo Capacity: 3
Grid: 10
Weight: 2000kg
The bots it would launch would either be Fennus Observers or a new class, and the same faction as the player who launched them. Once launched, the player/guild who owns them would be given access to the bots' armor status and sensor log. These bots would be stationary, have a sensor range of 5km, have some form of limited lifespan, and have a limit of how many the player/guild could have active at a time. Station defenses would treat them the same way as mines (fired upon by capgauss but left alone by station guards), unless a Serco bot is dropped at an Itani station or vice versa, in which case the station guards would attack them. If docked at a station or capital ship, the owner of the bot can remotely pilot it into sectors he or she wishes to monitor, but there would be some form of limit to how often it can jump to prevent quick blow-throughs.
So yeah...thoughts?
Of course we need in-game, player controlled bot networks. Of course it's a good idea
It's even on the development agenda.
But like most things in VO, it's so far down the track that people aren't going to rely on the devs to put it there in the next two years, so they are going to take matters into their own hands, like with SCIN and PA's silly bot.
It's even on the development agenda.
But like most things in VO, it's so far down the track that people aren't going to rely on the devs to put it there in the next two years, so they are going to take matters into their own hands, like with SCIN and PA's silly bot.
"Station defenses would treat them the same way as mines (fired upon by capgauss but left alone by station guards)"
Um, station guards do attack mines. At least the normal guards at normal stations do. I don't know whether conq-station guards treat them differently.
Um, station guards do attack mines. At least the normal guards at normal stations do. I don't know whether conq-station guards treat them differently.
That would be interesting. Good idea, Sam.
+1
+1
Um, station guards do attack mines. At least the normal guards at normal stations do. I don't know whether conq-station guards treat them differently.
Oh. Didn't know that.
Oh. Didn't know that.
TRS, you DO hopefully realize the the PhoenixVoice bot doesn't do any spying, right? I should know, I wrote all its code and do all its maintenance. I'd considered putting in a spotter, like we have for players, but decided against it.
The intent of PV is to provide IRC access for PA, run the casino, financial system, and eventually the bartender (provided I can ever find the time from all the other things I'm doing to actually get it more than just an embryonic chat agent) The intent for the bartender is to provide some of the things that have been mentioned, like selling information (that's why I've experimented with some data mining techniques from the chat channels in some of my experimental plugins I run on my character's client), virtual beer, as well as providing basic assistance. There are a couple of other things too, but they aren't done enough to discuss. (unless anybody wants to help build them - I'm trying very hard to make things under construction be guild neutral)
Anyway, back on task...
+1 to OP I can see how too many of the things would put a serious stress on the VO server, but the ability to perform recon (without having to rely on expensive bot networks) would be a useful addition to the game. (not to mention something that any subscribing player would have available)
The intent of PV is to provide IRC access for PA, run the casino, financial system, and eventually the bartender (provided I can ever find the time from all the other things I'm doing to actually get it more than just an embryonic chat agent) The intent for the bartender is to provide some of the things that have been mentioned, like selling information (that's why I've experimented with some data mining techniques from the chat channels in some of my experimental plugins I run on my character's client), virtual beer, as well as providing basic assistance. There are a couple of other things too, but they aren't done enough to discuss. (unless anybody wants to help build them - I'm trying very hard to make things under construction be guild neutral)
Anyway, back on task...
+1 to OP I can see how too many of the things would put a serious stress on the VO server, but the ability to perform recon (without having to rely on expensive bot networks) would be a useful addition to the game. (not to mention something that any subscribing player would have available)
Nice idea, yet I can see a way to get around the limitations you are suggesting. A player can have a main and an alt, or two accounts and so to main charters. Only one charter needs to be in the guild, the other (the 2nd main for a two account player, or the alt) would not need to be in the guild, yet could still have access to plug-ins and be aware of unpublished chat channels, so they could run their own little un-guilded network and just share the info with the guild.
And what happens if you have three charters, and each one is in a different guild, such as PA, FAMY, and RED? Could I have only three bots, and would they all have to be in one guild, or would I not be allowed any?
And who decides how many bots a guild gets? If is just one flat number, so you have 20 alts forming twenty guilds, and then forming an alliance with a larger guild, and sharing resources and information?
Nice idea, yet I still see the opportunity for abuse, and/or a way to work around the limitations you are imposing/suggesting.
And what happens if you have three charters, and each one is in a different guild, such as PA, FAMY, and RED? Could I have only three bots, and would they all have to be in one guild, or would I not be allowed any?
And who decides how many bots a guild gets? If is just one flat number, so you have 20 alts forming twenty guilds, and then forming an alliance with a larger guild, and sharing resources and information?
Nice idea, yet I still see the opportunity for abuse, and/or a way to work around the limitations you are imposing/suggesting.