-
Repository
It seems like Annoucements are harder to spot than normal threads so here it is, in a thread. Ask question about Git usage or Repo in general.
This is the link to GitHub repository.
https://github.com/razorapid/Reborn-PK3-Content.git (Read/Write)
git://github.com/razorapid/Reborn-PK3-Content.git (Read Only)
Few guidelines:
0. Rule number zero. Always include comment to your commit, and try to make it descriptive
1. Use "devel" branch for development. When your library, or functionality you've been working on is complete, merged it into "master" branch
2. Always update your local repository before you commit any changes
3. Commit only working code
4. If something doesn't work, create an Issue, so someone can take up on fixing this if you won't have time
5. At the end of the day commit all changes, with not working code commented out
Small tutorial:
1. Get the GIT client, I'm using it's portable version. You can get it from here: Portable GIT
2. Once you unpack it. Got to the Git folder, run git-bash.bat file (you can use other but bash like console is more flexible)
3. Type this to set up your name etc. so we can know who made changes and what are those changes:
Code:
$ git config --global user.name "Your name"
$ git config --global user.email "Your email"
4. Now create a folder for your repositiories (in this example, inside of Git Portable folder):
Code:
mkdir repositiories
5. Go to that folder: (you can press TAB to autocomplete)
6. Now clone the repository:
Code:
git clone https://github.com/razorapid/Reborn-PK3-Content.git
You will be asked for login and password, you have to register on GitHub and create an account
7. You have the repo on your HDD. Now you can make changes to it.
8. Move to devel branch by typing:
9. With
you can check in which branch you are currently working, and other available branches.
Standard workflow is like this:
* You make changes
* git pull -> do this before every commit to make sure you are up-to-date and to reduce the possibility of conflicts
* git add * -> adds any new files you put in the folder to repository revision control
* git commit -m "Commit comment" -> this commits changes to local git repo
* git push -> pushes the changes from local git repo to the server
More detailed tutorial here:
http://learn.github.com/p/intro.html
-
I'll try to get something up there this weekend.
-
Well to be honest, I'm not sure what else needs to be added to the reborn pk3 already out there...
-
Check this thread to get the idea what I wanted to do:
http://www.x-null.net/forums/showthr...new-Reborn-pk3
You can start with adding strings.scr, files.scr, math.scr
Then you can write datetime.scr .
We'll also need players.scr with different functions like: getPlayerById, getPlayerByClientnum, getPlayerByIP, ... , getPlayersWithName, getPlayersWith (certain weapon maybe) and so on.
Then we'll need to revise the code, look for bugs etc. We just need to start with something.
-
1 Attachment(s)
I won't have much time this week to check this out, but I've updated maths.scr myself:
Attachment 648
I think it's the most complete and up-to-date version yet with all the functions jv_map and veers wrote (plus 2 elementary-school-grade maths functions I wrote).
I've also made it possible to execute the main/first thread of the script in order to be able to access all of the functions by means of level. variables.
-
Nice, than you a lot. I'll try to add this to repo.
-
I tried to add a hud.scr for getting ihud and hud ID's but get the following error:
Username for 'https://github.com':
Password for 'https://cgarmageddon@github.com':
error: The requested URL returned error: 403 while accessing https://github.com/
razorapid/Reborn-PK3-Content.git/info/refs
fatal: HTTP request failed
I am signed up on github.com
-
1 Attachment(s)
Well, since I can't seem to push it to the server, here's something to start with.
By the way.... I couldn't get waitexec level.packageName.methodName to work. I had to use waitexec level.methodName, as you will see in the .pk3 ?? I don't understand why????
-
Try now. I've aaded you as a collaborator
I'll also need others nicknames on GitHub.
Armageddon, you will have to create a listener, because only a listener can hold list of variables (accessible with dot)
This is how Elgan did it in files.scr:
Code:
// Build the file
local.file = local CreateListener
//give this file a targetname
local.file targetname "files"
local.file.filename = local.filename
local.file.accesstype = local.accesstype
local.file.isopen = 0 //false
local.file.handle = NIL
local.file.keepopen = 0
local.file.dontflush = 0
local.file.id = level.fileid
local.file.autosave = 1
local.file.position = 0
local.file.parsedsections = 0
local.file.beingaccessed = 0
local.file.autoinitodata = 1
//build the threads
local.file.close = global/files.scr::("close" + local.file.id)
local.file.open = global/files.scr::("open" + local.file.id)
.. and so on ..
local, level, owner, self are all just listeners. local.player is also a listener because Entity inherits from Listener
You can rework the script and add it to the repo. Now you should be able to do so.
-
Haven't checked the script yet but 'Listeners' cannot be spawned before level waittill spawn. Use 'SimpleEntity' if you want to use entity-based data structs before waittill spawn.