Bukkit

@Joxiscraft

Errors starts with something like:

2013-06-02 18:16:19 [SEVERE] Could not pass event PlayerInteractEvent to blFCP v0.0.9.7
org.bukkit.event.EventException
	at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:427)
	at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62)

I have heard tho that some hosts cuts down amount of lines you get, killing error messages :/ I will take look if I catch that error at some point,.

@Joxiscraft

I would need longer version of that bug, you can paste it here: http://dev.bukkit.org/paste/ try and include at least lines which has "caused by:" and following few lines, like:

Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at net.blcraft.blFCP.FactionsWG.CaptureSign(FactionsWG.java:459)

I can provide you pre-update version after I have received that full error so I can take better look.

Update going quite nice, will include first attempt at "buff rewards", I had following idea:

config.yml would have list, such as:

Buff-Regions:
- MyRegion:<potion-id>:<potion-duration:<potion-power>

FCP would give out potion effects to all Capture Point owner faction online players at each check. You can also do like

Buff-Regions:
- MyRegion:remove

which would remove all negative potion effects. So thats the idea, if you have any suggestions related to "buff" feature, feel free to shoot comment.

@ArdiniusK

Do you have "Wait-Check" set as true? You can send me IP if you want, tho not sure how I can help there as its most likely related to config.yml settings.

@TomYaMee

I try and solve every ticket before I release update, but something things might not be fixed 100% but eventually (I hope) they will. Shitty situation is, I dont have any active server running so only bug reports I get is from users, I have to check only with 2 players (1 at each faction) so cant do any "in-depth" testing :( I will look into activity settings if I can hook into that somehow.

Small delay which means some more fixes. I will remove "random region naming" feature, you must define region name before creation Capture Point (if you have Region-Creation: true), I think random region naming is causing bit too much confusion.

As far testing goes, "automatic remove Capture Point if sign is missing" seems to work, at lest I havent noticed any bugs while creating update. If you are in hurry to get latest update, you can send private message to me and I will provide most recent test build, otherwise Im hoping to get this update out by sunday. In case you wonder, I get some error reports via private messages, new error means delay as I try to provide less bugs with each update :P

Next update should come this friday, looking into adding optional buff rewards but no promises :)

@predawnia

While ago I had an idea to include potion buffs which would gives defined buff at every Capture Check, but since there was no intrest on that I decided to focus into different things. I can look into this while creating current update, if I can manage to do it in smart way.

That wraps up today, "automatic Capture Point fix" completed and off to sleep, 6 hours before work. Again, if you want "dev of the dev build" then feel free to comment / pm me, as next full update will take few days at least. Smaller changes remains for tmr.

I will send message here once test server is open again tmr.

If anyone wants "dev of the dev build" feel free to comment/send me private message, next update is taking bit longer since "bug fix" list is getting bigger each time I fix one bug.

Main thing Im doing now is "automatic Capture Point fix"; which means if there is Capture Point registered but no sign found then FCP will remove that Capture Point at next "CapturePoint Check".

@willkiller1234

Private message send, its not complete update but contains fixes for FCP setup while having Region-Creation false.

Skipping 0.0.9.7.5 update, 0.0.9.8 coming tmr, there were more problems than I orginally thought, so current changelog looks like..

1) Allow to setup Capture Points to existing region.
2) Allow to break/place chests inside region IF Chest-Search is disabled. Only affects regions that contains Capture Points which is owned by faction.

Problem was if you created Capture Point in region while having Region-Creation: false, Capture Point was created but region still had wrong setup, missing Region-Priority. This hopefully fixes all the problems with regions (building inside capture region etc.).

@willkiller1234

I have now tested with Region-Creation: false and Region-Creation true, WorldGuard 5.7.3 and 5.7.4, I cant reproduce bug you mentioned. Region creation blocking is working for me and no regions/capture points are created if error message appears.

About that members not being able to build inside region, it seems to affect only placing blocks which hopefully Im able to fix in next quick update 0.0.9.8 that contains mostly bug/feature fixed, hoping monday release but within next 2 days is quite certain.

@willkiller1234

I tested with both Region-Creation true and false. I have feeling there is something with WorldGuard previous versions, I will start testing after shower to see where is the problem.

@willkiller1234 Each Capture Point settings (xp or money reward amounts, time lock etc..) can be unique, if you are talking about "Wait-Check" timer how long it runs and such, that is global option for now. Once WorldGuard allows custom flags (without need for another plugin) I can allow more flexible settings for each regions. If I misunderstood question, feel free to ask again.

For the bug, I tried following.
- Create Capture Point inside existing regions.
plugin blocks attempt and gives error that there is already region.

- Create Capture Point sign outside region zone.
sign is setup as it should.

It seems I cant reproduce this bug, if you have any more details that could help me, do tell and I try to look into it. If it helps, FCP is tested with 5.7.4 WorldGuard (http://build.sk89q.com/job/WorldGuard/846/). I made ticket (http://dev.bukkit.org/server-mods/fcp/tickets/5-fcp-created-region-even-if-it-should-be-disallowed/) just in case, will do small testing with different WG versions to see if problem is there.

I made small mistake in the update which is to disallow Capture Point setups inside existing region, since one of the feature requests were to use old regions instead FCP automatic regions, I will provide fix for it this weekend.