Actually, there’d be no rules on fitting for the explicit reason that disco smartbombing in highsec when someone catches you would be hilarious, and people should be free to choose their strategy for victory.
1 Like
Thanks mate. I’d thought of a more primitive system of making people retrieve items along the way, but the concern was just that-- somebody would steal everything to deprive the other racers. Audit logs would prevent that, but not somebody shooting the can. I’d like to avoid having to have many organizers/monitors/referees-- because then it might be so complicated that it might not ever happen.
What do you guys think of just announcing a high sec start station on the day of the race. One monitor is there to register who showed up. When GO is announced, also announce the destination station. The shortest route goes through low sec. (So there should be PVP opportunities among the racers along the way). A monitor is in that station to record when people dock and show up in the station’s Guests list.
Very simple and easy to administer, but:
-Jump clones-- Probably a non-issue. Just make the destination station in some isolated system, far from where anyone would likely have a JC.
WH shortcut issue-- People who know their WH entrances into high sec could take shortcuts. However, while they’re working out that route, they’re losing time to guys who just started warping the direct route. Any thoughts?
1 Like
EVE’s API is quite sophisticated these days. I vaguely recall seeing a warp race where the participants were tracked with a web interface through the API, similar to how Pathfinder works today to show you who is where in wormhole corps, etc…
My philosophy when designing race courses is a “rubber band” concept. Imagine that you put a pin on a map in the starting location, and then tie a band or string to that pin. Then you pull the string tight and tie it to a pin at the end location. The string will always take the shortest path from the start to the finish, and any additional checkpoints or obstacles you design into your race course need to bend the path of that string.
When I design a race, or any other activity, I always think in terms of adding requirements or goals, and I always try to avoid having to add restrictions.
To use your examples: If you don’t want people to use jump clones as part of the race, you need to design the race in such a way that jump clones would be slower, or less useful. For example, you could have racers bring a certain unique item from the start to the finish. That would eliminate the usefulness of jump clones.
One idea I toyed with several years ago in that regard was this: If I recall correctly, most items in EVE have a unique ID in the database. For example, an assembled ship has a unique ID, and if you repackage it and assemble it again, it receives a new unique ID. So maybe you can verify that participants arrive in the same exact ship they departed with. I thought about doing this with an itemized bookmark. You could record each player’s bookmark at the start of the race, and then check that they were still carrying the same bookmark at the end. Then you would know they could not have used jump clones.
2 Likes
Nice! That idea completely counters the JC issue. Tracking through API, (even if only some of the racers can actually be tracked) should take out any incentive or WH-shortcutting. Simple solution.
So we’ve got three prospective events cooking:
-Warping dogleg through lowsec
-Highsec BS race-free for all
-Scavenger hunt
Plus Orca space futbol
1 Like
The idea of issuing a Destination Bookmark to each racer at the start line in station which they have to carry to the finish line in another station is good, definitely will keep Jump Clones from being used.
Could even make it have multiple stages with station check-in points spread around the cluster. Time starts when ship undocks from each starting station and time stops when ship docks at each destination station. The start time could be listed by someone sitting in station issuing the Destination Bookmarks and the finish time logged by someone in station collecting the Bookmark at the Destination station.
Could have various ‘Winner’ categories, such as racer with fastest time for each stage and of course the racer with the fastest time overall.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.