spyfall | Spyfall | Web Framework library

Per the Meteor API, Meteor methods are meant to be the way you define server side behavior that you call from the client. They are really intended to be defined on the server.

Methods are remote functions that Meteor clients can invoke with Meteor.call.

A Meteor method defined on the client simply acts as a stub.

Calling methods on the client defines stub functions associated with server methods of the same name

Based on your code it looks like you are doing everything client side. In fact, session is part of the Meteor client API (can't use on the server).

Session provides a global object on the client that you can use to store an arbitrary set of key-value pairs.

Therefore, If I were you, I would just implement all this logic in some sort of util file that you can then import into the Templates where you need it. You are effectively doing the same thing, you just need to use regular functions instead of Meteor methods.

Here is an example util file (be sure to update the Players import based upon your project's file structure).